Closed kmerguerian closed 9 years ago
elizoller
commented
9 years ago I think this might be because when I do a search directly for this article in SoS it doesn't show up that we have it so then the permalink function can't find an item with that id. I'm not really sure why it doesn't show up in SoS but if you go through CINAHL, we do have it? Maybe @jdevanna can explain it to me?
kmerguerian
commented
9 years ago Yes I noticed that also--Maybe we should not offer a permalink in this situation then?
Karen Merguerian User Services Northeastern University Libraries
On Mar 25, 2015, at 8:01 AM, "Eli Zoller" notifications@github.com<mailto:notifications@github.com> wrote:
I think this might be because when I do a search directly for this article in SoS it doesn't show up that we have it so then the permalink function can't find an item with that id. I'm not really sure why it doesn't show up in SoS but if you go through CINAHL, we do have it? Maybe @jdevannahttps://github.com/jdevanna can explain it to me?
Reply to this email directly or view it on GitHubhttps://github.com/NEU-Libraries/scholar-onesearch/issues/174#issuecomment-85999115.
jdevanna
commented
9 years ago I think what's going on here is that the metadata being passed through the link resolver is creating a "temporary" record, basically just a display of the metadata, somehow the permalink function is creating an id when the permalink is generated, however since it is not actually a record in primo, there is no way to link back to it. There would need to be someway to actually pass the URL of the initial open URL request into the report a problem form instead of the permalink when it is not actually a record in primo, if that makes sense
For example, the only way to link back to the record generated by the link resolver is:
I have no idea how the system is generating:
http://onesearch.library.northeastern.edu/NU:RS_6102860201094hyticfungusconiothyriumsp
I'll open a case with ExLibris to see if they can explain how this is generated.
elizoller
commented
9 years ago I believe the string comes from NU being the view id and after the colon is the id of the .EXLResultRecordId item in the result dom. So it's some kind of unique identifier per result. Not sure where that id is generated by EXL though
kmerguerian
commented
9 years ago That makes perfect sense! But from a user viewpoint we can't be offering a permalink that is in fact a temporary link. Thanks for offering to open a ticket.
Karen Merguerian User Services Northeastern University Libraries
On Mar 25, 2015, at 8:39 AM, "jdevanna" notifications@github.com<mailto:notifications@github.com> wrote:
I think what's going on here is that the metadata being passed through the link resolver is creating a "temporary" record, basically just a display of the metadata, somehow the permalink function is creating an id when the permalink is generated, however since it is not actually a record in primo, there is no way to link back to it. There would need to be someway to actually pass the URL of the initial open URL request into the report a problem form instead of the permalink when it is not actually a record in primo, if that makes sense
For example, the only way to link back to the record generated by the link resolver is:
http://onesearch.library.northeastern.edu/primo_library/libweb/action/openurl?dscnt=1&genre=article&spage=1094&sid=EBSCO%3ACINAHL+Complete&isSerivcesPage=true&url_ctx_fmt=null&issn=10286020&issue=11&pages=1094-1098&dstmp=1427287006153&date=20141101&aulast=Hussain%2C+Hidayat&atitle=Coniothyren%3A+a+new+phenoxyphenyl+ether+from+th e+endoph ytic+fungus%2C+Coniothyrium+sp.&title=Journal+of+Asian+Natural+Products+Research&isbn=&volume=16&vid=neu_services_page&doi=10.1080%2F10286020.2014.931843&institution=NEU&fromLogin=truehttp://onesearch.library.northeastern.edu/primo_library/libweb/action/openurl?dscnt=1&genre=article&spage=1094&sid=EBSCO%3ACINAHL+Complete&isSerivcesPage=true&url_ctx_fmt=null&issn=10286020&issue=11&pages=1094-1098&dstmp=1427287006153&date=20141101&aulast=Hussain%2C+Hidayat&atitle=Coniothyren%3A+a+new+phenoxyphenyl+ether+from+the+endophytic+fungus%2C+Coniothyrium+sp.&title=Journal+of+Asian+Natural+Products+Research&isbn=&volume=16&vid=neu_services_page&doi=10.1080%2F10286020.2014.931843&institution=NEU&fromLogin=true
I have no idea how the system is generating:
http://onesearch.library.northeastern.edu/NU:RS_6102860201094hyticfungusconiothyriumsp
I'll open a case with ExLibris to see if they can explain how this is generated.
Reply to this email directly or view it on GitHubhttps://github.com/NEU-Libraries/scholar-onesearch/issues/174#issuecomment-86008758.
elizoller
commented
9 years ago Should I disable permalink functionality on the neu_services_page view?
kmerguerian
commented
9 years ago Question for READ perhaps?
Karen Merguerian User Services Northeastern University Libraries
On Mar 25, 2015, at 8:51 AM, "Eli Zoller" notifications@github.com<mailto:notifications@github.com> wrote:
Should I disable permalink functionality on the neu_services_page view?
Reply to this email directly or view it on GitHubhttps://github.com/NEU-Libraries/scholar-onesearch/issues/174#issuecomment-86010717.
jdevanna
commented
9 years ago It sometimes provides a portion of the article title which allows me to search and pull up a related record, so it is somewhat useful
elizoller
commented
9 years ago I'm also only able to get the permalink to work one time in the same browser. So it's not exactly permanent.
winthropo
commented
9 years ago I think we should disable the SOS permalink we get coming from CINHAL etc. The permalink in SOS seems to be working fine.
elizoller
commented
9 years ago Deployed
Example:
Find this journal article in CINAHL http://ezproxy.neu.edu/login?url=http://search.ebscohost.com/login.aspx?direct=true&db=ccm&AN=2012792819&site=ehost-live&scope=site
Click on "Check for Full Text" Go to "Permalink" on the resulting SoS page Paste the permalink into another browser. You get the blank SoS screen with the little yellow dot.
This is happening to me in iOS with Safari and Firefox.