Opened 10 years ago

Closed 9 years ago

#604 closed enhancement (wontfix)

Save JSTOR links as EZproxy links (?)

Reported by: dstillman Owned by: simon
Priority: minor Milestone: 1.0 RC 4
Component: ingester Version: 1.0
Keywords: Cc: stakats

Description

JSTOR snapshots used to be EZproxy URLs, but the new links are not. Does it make sense use EZproxy links instead?

Really there's probably value in both. Does EZproxy work such that you can send any link at a specific URL? Is it something that could just be configured, and then regular links could be sent through the EZproxy login page, or is that not possible?

Change History (2)

comment:1 Changed 10 years ago by dstillman

While we're on the subject, why are we saving links at all on JSTOR if the URL is already stored in the URL field? It might make sense if the URL field was the regular link and the other was EZProxy (if just sending links at a URL like I mentioned above isn't possible), but not if they're the same...

comment:2 Changed 9 years ago by simon

  • Resolution set to wontfix
  • Status changed from new to closed

The best solution to this problem, I believe, is to remember where the EZProxy is and transparently route users through it. I describe this in further detail in #743. It doesn't seem to make sense to implement this separately.

Note: See TracTickets for help on using tickets.