Re: [CODE4LIB] OpenURL linking but from the content provider's point of view
If David is coining his own ContextObjects, he could add his own Linked Data rft_id in addition to or instead of the dx.doi.org URI. The rft_id key is repeatable. If he does coins his own Linked Data URI, though, I would recommend having his Linked Data URI assert owl:sameAs with the dx.doi.org URI in the RDF. OTOH, if he's merely consuming ContextObjects via his own OpenURL Resolver and wants to deliver the content locally, he treat the dx.doi.org URI as a mere identifier and direct the requester to the copy he is hosting instead. Jeff > -Original Message- > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of > Jason Stirnaman > Sent: Wednesday, November 21, 2012 10:20 AM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] OpenURL linking but from the content provider's > point of view > > Sorry. I guess I misunderstood. I thought David meant resolving > OpenURLs pointed at his content. > > Jason > > Jason Stirnaman > Digital Projects Librarian > A.R. Dykes Library > University of Kansas Medical Center > 913-588-7319 > > > From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of > Young,Jeff (OR) [jyo...@oclc.org] > Sent: Wednesday, November 21, 2012 9:08 AM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] OpenURL linking but from the content provider's > point of view > > If the referent has a DOI, then I would argue that > rft_id=http://dx.doi.org/10.1145/2132176.2132212 is all you need. The > descriptive information that typically goes in the ContextObject can be > obtained (if necessary) by content-negotiating for application/rdf+xml. > OTOH, if someone pokes this same URI from a browser instead, you will > generally get redirected to the publisher's web site with the full-text > close at hand. > > The same principle should apply for any bibliographic resource that has > a Linked Data identifier. > > Jeff > > > -Original Message- > > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf > Of > > Owen Stephens > > Sent: Wednesday, November 21, 2012 9:55 AM > > To: CODE4LIB@LISTSERV.ND.EDU > > Subject: Re: [CODE4LIB] OpenURL linking but from the content > provider's > > point of view > > > > The only difference between COinS and a full OpenURL is the addition > of > > a link resolver address. Most databases that provide OpenURL links > > directly (rather than simply COinS) use some profile information - > > usually set by the subscribing library, although some based on > > information supplied by an individual user. If set by the library > this > > is then linked to specific users by IP or by login. > > > > There are a couple(?) of generic base URLs you can use which will try > > to redirect to an appropriate link resolver based on IP range of the > > requester, with fallback options if it can't find an appropriate > > resolver (I think this is how the WorldCat resolver works? The > 'OpenURL > > Router' in the UK definitely works like this) > > > > The LibX toolbar allows users to set their link resolver address, and > > then translates COinS into OpenURLs when you view a page - all user > > driven, no need for the data publisher to do anything beyond COinS > > > > There is also the 'cookie pusher' solution which ArXiv uses - where > the > > user can set a cookie containing the base URL, and this is picked up > > and used by ArXiV (http://arxiv.org/help/openurl) > > > > Owen > > > > PS it occurs to me that the other part of the question is 'what > > metadata should be included in the OpenURL to give it the best chance > > of working with a link resolver'? > > > > Owen Stephens > > Owen Stephens Consulting > > Web: http://www.ostephens.com > > Email: o...@ostephens.com > > Telephone: 0121 288 6936 > > > > On 20 Nov 2012, at 19:39, David Lawrence > > wrote: > > > > > I have some experience with the library side of link resolver code. > > > However, we want to implement OpenURL hooks on our open access > > > literature database and I can not find where to begin. > > > > > > SafetyLit is a free service of San Diego State University in > > > cooperation with the World Health Organization. We already provide > > > embedded metadata in both COinS and unAPI formats to allow its > > capture > > > by Mendeley, Papers, Zotero, etc. Over the past few months, I have > > > emailed or talked with many people and read everything I can get my > >
Re: [CODE4LIB] OpenURL linking but from the content provider's point of view
Sorry. I guess I misunderstood. I thought David meant resolving OpenURLs pointed at his content. Jason Jason Stirnaman Digital Projects Librarian A.R. Dykes Library University of Kansas Medical Center 913-588-7319 From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Young,Jeff (OR) [jyo...@oclc.org] Sent: Wednesday, November 21, 2012 9:08 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] OpenURL linking but from the content provider's point of view If the referent has a DOI, then I would argue that rft_id=http://dx.doi.org/10.1145/2132176.2132212 is all you need. The descriptive information that typically goes in the ContextObject can be obtained (if necessary) by content-negotiating for application/rdf+xml. OTOH, if someone pokes this same URI from a browser instead, you will generally get redirected to the publisher's web site with the full-text close at hand. The same principle should apply for any bibliographic resource that has a Linked Data identifier. Jeff > -Original Message- > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of > Owen Stephens > Sent: Wednesday, November 21, 2012 9:55 AM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] OpenURL linking but from the content provider's > point of view > > The only difference between COinS and a full OpenURL is the addition of > a link resolver address. Most databases that provide OpenURL links > directly (rather than simply COinS) use some profile information - > usually set by the subscribing library, although some based on > information supplied by an individual user. If set by the library this > is then linked to specific users by IP or by login. > > There are a couple(?) of generic base URLs you can use which will try > to redirect to an appropriate link resolver based on IP range of the > requester, with fallback options if it can't find an appropriate > resolver (I think this is how the WorldCat resolver works? The 'OpenURL > Router' in the UK definitely works like this) > > The LibX toolbar allows users to set their link resolver address, and > then translates COinS into OpenURLs when you view a page - all user > driven, no need for the data publisher to do anything beyond COinS > > There is also the 'cookie pusher' solution which ArXiv uses - where the > user can set a cookie containing the base URL, and this is picked up > and used by ArXiV (http://arxiv.org/help/openurl) > > Owen > > PS it occurs to me that the other part of the question is 'what > metadata should be included in the OpenURL to give it the best chance > of working with a link resolver'? > > Owen Stephens > Owen Stephens Consulting > Web: http://www.ostephens.com > Email: o...@ostephens.com > Telephone: 0121 288 6936 > > On 20 Nov 2012, at 19:39, David Lawrence > wrote: > > > I have some experience with the library side of link resolver code. > > However, we want to implement OpenURL hooks on our open access > > literature database and I can not find where to begin. > > > > SafetyLit is a free service of San Diego State University in > > cooperation with the World Health Organization. We already provide > > embedded metadata in both COinS and unAPI formats to allow its > capture > > by Mendeley, Papers, Zotero, etc. Over the past few months, I have > > emailed or talked with many people and read everything I can get my > > hands on about this but I'm clearly not finding the right people or > information sources. > > > > Please help me to find references to examples of the code that is > > required on the literature database server that will enable library > > link resolvers to recognize the SafetyLit.org metadata and allow > > appropriate linking to full text. > > > > SafetyLit.org receives more than 65,000 unique (non-robot) visitors > > and the database responds to almost 500,000 search queries every > week. > > The most frequently requested improvement is to add link resolver > capacity. > > > > I hope that code4lib users will be able to help. > > > > Best regards, > > > > David > > > > David W. Lawrence, PhD, MPH, Director > > Center for Injury Prevention Policy and Practice San Diego State > > University, School of Public Health > > 6475 Alvarado Road, Suite 105 > > San Diego, CA 92120 usadavid.lawre...@sdsu.edu > > V 619 594 1994 F 619 594 1995 Skype: DWL-SDCAwww.CIPPP.org -- > > www.SafetyLit.org
Re: [CODE4LIB] OpenURL linking but from the content provider's point of view
Failure rate on resolving DOIs via CrossRef is high enough that I'd argue for belt && braces Owen Owen Stephens Owen Stephens Consulting Web: http://www.ostephens.com Email: o...@ostephens.com Telephone: 0121 288 6936 On 21 Nov 2012, at 15:08, "Young,Jeff (OR)" wrote: > If the referent has a DOI, then I would argue that > rft_id=http://dx.doi.org/10.1145/2132176.2132212 is all you need. The > descriptive information that typically goes in the ContextObject can be > obtained (if necessary) by content-negotiating for application/rdf+xml. > OTOH, if someone pokes this same URI from a browser instead, you will > generally get redirected to the publisher's web site with the full-text > close at hand. > > The same principle should apply for any bibliographic resource that has > a Linked Data identifier. > > Jeff > >> -Original Message- >> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf > Of >> Owen Stephens >> Sent: Wednesday, November 21, 2012 9:55 AM >> To: CODE4LIB@LISTSERV.ND.EDU >> Subject: Re: [CODE4LIB] OpenURL linking but from the content > provider's >> point of view >> >> The only difference between COinS and a full OpenURL is the addition > of >> a link resolver address. Most databases that provide OpenURL links >> directly (rather than simply COinS) use some profile information - >> usually set by the subscribing library, although some based on >> information supplied by an individual user. If set by the library this >> is then linked to specific users by IP or by login. >> >> There are a couple(?) of generic base URLs you can use which will try >> to redirect to an appropriate link resolver based on IP range of the >> requester, with fallback options if it can't find an appropriate >> resolver (I think this is how the WorldCat resolver works? The > 'OpenURL >> Router' in the UK definitely works like this) >> >> The LibX toolbar allows users to set their link resolver address, and >> then translates COinS into OpenURLs when you view a page - all user >> driven, no need for the data publisher to do anything beyond COinS >> >> There is also the 'cookie pusher' solution which ArXiv uses - where > the >> user can set a cookie containing the base URL, and this is picked up >> and used by ArXiV (http://arxiv.org/help/openurl) >> >> Owen >> >> PS it occurs to me that the other part of the question is 'what >> metadata should be included in the OpenURL to give it the best chance >> of working with a link resolver'? >> >> Owen Stephens >> Owen Stephens Consulting >> Web: http://www.ostephens.com >> Email: o...@ostephens.com >> Telephone: 0121 288 6936 >> >> On 20 Nov 2012, at 19:39, David Lawrence >> wrote: >> >>> I have some experience with the library side of link resolver code. >>> However, we want to implement OpenURL hooks on our open access >>> literature database and I can not find where to begin. >>> >>> SafetyLit is a free service of San Diego State University in >>> cooperation with the World Health Organization. We already provide >>> embedded metadata in both COinS and unAPI formats to allow its >> capture >>> by Mendeley, Papers, Zotero, etc. Over the past few months, I have >>> emailed or talked with many people and read everything I can get my >>> hands on about this but I'm clearly not finding the right people or >> information sources. >>> >>> Please help me to find references to examples of the code that is >>> required on the literature database server that will enable library >>> link resolvers to recognize the SafetyLit.org metadata and allow >>> appropriate linking to full text. >>> >>> SafetyLit.org receives more than 65,000 unique (non-robot) visitors >>> and the database responds to almost 500,000 search queries every >> week. >>> The most frequently requested improvement is to add link resolver >> capacity. >>> >>> I hope that code4lib users will be able to help. >>> >>> Best regards, >>> >>> David >>> >>> David W. Lawrence, PhD, MPH, Director >>> Center for Injury Prevention Policy and Practice San Diego State >>> University, School of Public Health >>> 6475 Alvarado Road, Suite 105 >>> San Diego, CA 92120 usadavid.lawre...@sdsu.edu >>> V 619 594 1994 F 619 594 1995 Skype: DWL-SDCAwww.CIPPP.org -- >>> www.SafetyLit.org
Re: [CODE4LIB] OpenURL linking but from the content provider's point of view
> The same principle should apply for any bibliographic resource that has a > Linked Data identifier. ...the difference being that with a DOI you have at least in principle some guarantee of what sort of stuff is on the end of the URI (and of it still being there). See http://www.doi.org/doi_handbook/5_Applications.html#5.4 > PS it occurs to me that the other part of the question is 'what > metadata should be included in the OpenURL to give it the best chance > of working with a link resolver'? For DOIs there is a simple answer to this: http://www.doi.org/doi_handbook/4_Data_Model.html#4.3.1 - for specific implementations, there's a domain-specific set. -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Young,Jeff (OR) Sent: 21 November 2012 15:09 To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] OpenURL linking but from the content provider's point of view If the referent has a DOI, then I would argue that rft_id=http://dx.doi.org/10.1145/2132176.2132212 is all you need. The descriptive information that typically goes in the ContextObject can be obtained (if necessary) by content-negotiating for application/rdf+xml. OTOH, if someone pokes this same URI from a browser instead, you will generally get redirected to the publisher's web site with the full-text close at hand. The same principle should apply for any bibliographic resource that has a Linked Data identifier. Jeff > -Original Message- > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of > Owen Stephens > Sent: Wednesday, November 21, 2012 9:55 AM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] OpenURL linking but from the content provider's > point of view > > The only difference between COinS and a full OpenURL is the addition of > a link resolver address. Most databases that provide OpenURL links > directly (rather than simply COinS) use some profile information - > usually set by the subscribing library, although some based on > information supplied by an individual user. If set by the library this > is then linked to specific users by IP or by login. > > There are a couple(?) of generic base URLs you can use which will try > to redirect to an appropriate link resolver based on IP range of the > requester, with fallback options if it can't find an appropriate > resolver (I think this is how the WorldCat resolver works? The 'OpenURL > Router' in the UK definitely works like this) > > The LibX toolbar allows users to set their link resolver address, and > then translates COinS into OpenURLs when you view a page - all user > driven, no need for the data publisher to do anything beyond COinS > > There is also the 'cookie pusher' solution which ArXiv uses - where the > user can set a cookie containing the base URL, and this is picked up > and used by ArXiV (http://arxiv.org/help/openurl) > > Owen > > > Owen Stephens > Owen Stephens Consulting > Web: http://www.ostephens.com > Email: o...@ostephens.com > Telephone: 0121 288 6936 > > On 20 Nov 2012, at 19:39, David Lawrence > wrote: > > > I have some experience with the library side of link resolver code. > > However, we want to implement OpenURL hooks on our open access > > literature database and I can not find where to begin. > > > > SafetyLit is a free service of San Diego State University in > > cooperation with the World Health Organization. We already provide > > embedded metadata in both COinS and unAPI formats to allow its > capture > > by Mendeley, Papers, Zotero, etc. Over the past few months, I have > > emailed or talked with many people and read everything I can get my > > hands on about this but I'm clearly not finding the right people or > information sources. > > > > Please help me to find references to examples of the code that is > > required on the literature database server that will enable library > > link resolvers to recognize the SafetyLit.org metadata and allow > > appropriate linking to full text. > > > > SafetyLit.org receives more than 65,000 unique (non-robot) visitors > > and the database responds to almost 500,000 search queries every > week. > > The most frequently requested improvement is to add link resolver > capacity. > > > > I hope that code4lib users will be able to help. > > > > Best regards, > > > > David > > > > David W. Lawrence, PhD, MPH, Director Center for Injury Prevention > > Policy and Practice San Diego State University, School of Public > > Health > > 6475 Alvarado Road, Suite 105 > > San Diego, CA 92120 usadavid.lawre...@sdsu.edu > > V 619 594 1994 F 619 594 1995 Skype: DWL-SDCAwww.CIPPP.org -- > > www.SafetyLit.org
Re: [CODE4LIB] OpenURL linking but from the content provider's point of view
If the referent has a DOI, then I would argue that rft_id=http://dx.doi.org/10.1145/2132176.2132212 is all you need. The descriptive information that typically goes in the ContextObject can be obtained (if necessary) by content-negotiating for application/rdf+xml. OTOH, if someone pokes this same URI from a browser instead, you will generally get redirected to the publisher's web site with the full-text close at hand. The same principle should apply for any bibliographic resource that has a Linked Data identifier. Jeff > -Original Message- > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of > Owen Stephens > Sent: Wednesday, November 21, 2012 9:55 AM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] OpenURL linking but from the content provider's > point of view > > The only difference between COinS and a full OpenURL is the addition of > a link resolver address. Most databases that provide OpenURL links > directly (rather than simply COinS) use some profile information - > usually set by the subscribing library, although some based on > information supplied by an individual user. If set by the library this > is then linked to specific users by IP or by login. > > There are a couple(?) of generic base URLs you can use which will try > to redirect to an appropriate link resolver based on IP range of the > requester, with fallback options if it can't find an appropriate > resolver (I think this is how the WorldCat resolver works? The 'OpenURL > Router' in the UK definitely works like this) > > The LibX toolbar allows users to set their link resolver address, and > then translates COinS into OpenURLs when you view a page - all user > driven, no need for the data publisher to do anything beyond COinS > > There is also the 'cookie pusher' solution which ArXiv uses - where the > user can set a cookie containing the base URL, and this is picked up > and used by ArXiV (http://arxiv.org/help/openurl) > > Owen > > PS it occurs to me that the other part of the question is 'what > metadata should be included in the OpenURL to give it the best chance > of working with a link resolver'? > > Owen Stephens > Owen Stephens Consulting > Web: http://www.ostephens.com > Email: o...@ostephens.com > Telephone: 0121 288 6936 > > On 20 Nov 2012, at 19:39, David Lawrence > wrote: > > > I have some experience with the library side of link resolver code. > > However, we want to implement OpenURL hooks on our open access > > literature database and I can not find where to begin. > > > > SafetyLit is a free service of San Diego State University in > > cooperation with the World Health Organization. We already provide > > embedded metadata in both COinS and unAPI formats to allow its > capture > > by Mendeley, Papers, Zotero, etc. Over the past few months, I have > > emailed or talked with many people and read everything I can get my > > hands on about this but I'm clearly not finding the right people or > information sources. > > > > Please help me to find references to examples of the code that is > > required on the literature database server that will enable library > > link resolvers to recognize the SafetyLit.org metadata and allow > > appropriate linking to full text. > > > > SafetyLit.org receives more than 65,000 unique (non-robot) visitors > > and the database responds to almost 500,000 search queries every > week. > > The most frequently requested improvement is to add link resolver > capacity. > > > > I hope that code4lib users will be able to help. > > > > Best regards, > > > > David > > > > David W. Lawrence, PhD, MPH, Director > > Center for Injury Prevention Policy and Practice San Diego State > > University, School of Public Health > > 6475 Alvarado Road, Suite 105 > > San Diego, CA 92120 usadavid.lawre...@sdsu.edu > > V 619 594 1994 F 619 594 1995 Skype: DWL-SDCAwww.CIPPP.org -- > > www.SafetyLit.org
Re: [CODE4LIB] OpenURL linking but from the content provider's point of view
The only difference between COinS and a full OpenURL is the addition of a link resolver address. Most databases that provide OpenURL links directly (rather than simply COinS) use some profile information - usually set by the subscribing library, although some based on information supplied by an individual user. If set by the library this is then linked to specific users by IP or by login. There are a couple(?) of generic base URLs you can use which will try to redirect to an appropriate link resolver based on IP range of the requester, with fallback options if it can't find an appropriate resolver (I think this is how the WorldCat resolver works? The 'OpenURL Router' in the UK definitely works like this) The LibX toolbar allows users to set their link resolver address, and then translates COinS into OpenURLs when you view a page - all user driven, no need for the data publisher to do anything beyond COinS There is also the 'cookie pusher' solution which ArXiv uses - where the user can set a cookie containing the base URL, and this is picked up and used by ArXiV (http://arxiv.org/help/openurl) Owen PS it occurs to me that the other part of the question is 'what metadata should be included in the OpenURL to give it the best chance of working with a link resolver'? Owen Stephens Owen Stephens Consulting Web: http://www.ostephens.com Email: o...@ostephens.com Telephone: 0121 288 6936 On 20 Nov 2012, at 19:39, David Lawrence wrote: > I have some experience with the library side of link resolver code. > However, we want to implement OpenURL hooks on our open access literature > database and I can not find where to begin. > > SafetyLit is a free service of San Diego State University in cooperation > with the World Health Organization. We already provide embedded metadata in > both COinS and unAPI formats to allow its capture by Mendeley, Papers, > Zotero, etc. Over the past few months, I have emailed or talked with many > people and read everything I can get my hands on about this but I'm clearly > not finding the right people or information sources. > > Please help me to find references to examples of the code that is required > on the literature database server that will enable library link resolvers > to recognize the SafetyLit.org metadata and allow appropriate linking to > full text. > > SafetyLit.org receives more than 65,000 unique (non-robot) visitors and the > database responds to almost 500,000 search queries every week. The most > frequently requested improvement is to add link resolver capacity. > > I hope that code4lib users will be able to help. > > Best regards, > > David > > David W. Lawrence, PhD, MPH, Director > Center for Injury Prevention Policy and Practice > San Diego State University, School of Public Health > 6475 Alvarado Road, Suite 105 > San Diego, CA 92120 usadavid.lawre...@sdsu.edu > V 619 594 1994 F 619 594 1995 Skype: DWL-SDCAwww.CIPPP.org -- > www.SafetyLit.org
Re: [CODE4LIB] OpenURL linking but from the content provider's point of view
- Original Message - > Date: Tue, 20 Nov 2012 11:39:17 -0800 > From: David Lawrence > Subject: OpenURL linking but from the content provider's point of view > > I have some experience with the library side of link resolver code. > However, we want to implement OpenURL hooks on our open access > literature database and I can not find where to begin. > > SafetyLit is a free service of San Diego State University in > cooperation with the World Health Organization. We already provide embedded > metadata in both COinS and unAPI formats to allow its capture by Mendeley, > Papers, > Zotero, etc. Over the past few months, I have emailed or talked with > many people and read everything I can get my hands on about this but I'm > clearly not finding the right people or information sources. > > Please help me to find references to examples of the code that is > required on the literature database server that will enable library link > resolvers to recognize the SafetyLit.org metadata and allow appropriate > linking > to full text. Unless I'm misunderstanding what you're after, link resolvers don't really "recognize metadata" from databases -- library link resolvers are sent metadata in an OpenURL when a user clicks a link that points to her resolver. Unless you plan on maintaining accounts for libraries and implementing IP address recognition so that each library's users will see a link to their institutional resolver when using your database (which is what the commercial databases do), the best approach might be to take advantage of the OCLC OpenURL resolver registry -- instead of having to generate OpenURLs that include institution-specific base URLs, you generate OpenURLs that point to worldcat, and the registry reformulates the OpenURL to point to the resolver associated with the user's IP address. This is the approach used by the Bibliography of Asian Studies at U Michigan; you might want to contact someone there for advice. Of course this approach only works for institutions whose resolvers a! re registered with OCLC and when users either have an institutional IP address or are going through an institution's proxy server. I imagine the code you use to generate the actual OpenURLs would likely be similar to the code you're using to generate COinS et. al. Bob Duncan ~!~!~!~!~!~!~!~!~!~!~!~!~ Robert E. Duncan Integrated Technologies Librarian David Bishop Skillman Library Lafayette College Easton, PA 18042 http://library.lafayette.edu/ dunc...@lafayette.edu
Re: [CODE4LIB] OpenURL linking but from the content provider's point of view
and wouldn't it be ideal if most applications took this approach and accepted incoming OpenURL? So many of the link resolution problems seem be when vendors change their interface and url structure breaking inbound requests until the link resolvers can get up to speed and adjust their parsers. Many of these same vendors create outbound OpenURL so it doesn't seem to be stretch to me that they could program for incoming. -- Jimmy Ghaphery Head, Library Information Systems VCU Libraries 804-827-3551 On Tue, Nov 20, 2012 at 3:23 PM, Jason Stirnaman wrote: > David, > The short answer is that your application needs to map keys and values > from the OpenURL query to your application's specific query interface. > DSpace supports OpenURL requests. You can find some of the relevant code > at: > > https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/src/main/java/org/dspace/app/xmlui/cocoon/OpenURLReader.java > > Jason Stirnaman > Digital Projects Librarian > A.R. Dykes Library > University of Kansas Medical Center > 913-588-7319 > > > From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of David > Lawrence [david.lawre...@sdsu.edu] > Sent: Tuesday, November 20, 2012 1:39 PM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: [CODE4LIB] OpenURL linking but from the content provider's point > of view > > I have some experience with the library side of link resolver code. > However, we want to implement OpenURL hooks on our open access literature > database and I can not find where to begin. > > SafetyLit is a free service of San Diego State University in cooperation > with the World Health Organization. We already provide embedded metadata in > both COinS and unAPI formats to allow its capture by Mendeley, Papers, > Zotero, etc. Over the past few months, I have emailed or talked with many > people and read everything I can get my hands on about this but I'm clearly > not finding the right people or information sources. > > Please help me to find references to examples of the code that is required > on the literature database server that will enable library link resolvers > to recognize the SafetyLit.org metadata and allow appropriate linking to > full text. > > SafetyLit.org receives more than 65,000 unique (non-robot) visitors and the > database responds to almost 500,000 search queries every week. The most > frequently requested improvement is to add link resolver capacity. > > I hope that code4lib users will be able to help. > > Best regards, > > David > > David W. Lawrence, PhD, MPH, Director > Center for Injury Prevention Policy and Practice > San Diego State University, School of Public Health > 6475 Alvarado Road, Suite 105 > San Diego, CA 92120 usadavid.lawre...@sdsu.edu > V 619 594 1994 F 619 594 1995 Skype: DWL-SDCAwww.CIPPP.org -- > www.SafetyLit.org >
Re: [CODE4LIB] OpenURL linking but from the content provider's point of view
David, The short answer is that your application needs to map keys and values from the OpenURL query to your application's specific query interface. DSpace supports OpenURL requests. You can find some of the relevant code at: https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/src/main/java/org/dspace/app/xmlui/cocoon/OpenURLReader.java Jason Stirnaman Digital Projects Librarian A.R. Dykes Library University of Kansas Medical Center 913-588-7319 From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of David Lawrence [david.lawre...@sdsu.edu] Sent: Tuesday, November 20, 2012 1:39 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] OpenURL linking but from the content provider's point of view I have some experience with the library side of link resolver code. However, we want to implement OpenURL hooks on our open access literature database and I can not find where to begin. SafetyLit is a free service of San Diego State University in cooperation with the World Health Organization. We already provide embedded metadata in both COinS and unAPI formats to allow its capture by Mendeley, Papers, Zotero, etc. Over the past few months, I have emailed or talked with many people and read everything I can get my hands on about this but I'm clearly not finding the right people or information sources. Please help me to find references to examples of the code that is required on the literature database server that will enable library link resolvers to recognize the SafetyLit.org metadata and allow appropriate linking to full text. SafetyLit.org receives more than 65,000 unique (non-robot) visitors and the database responds to almost 500,000 search queries every week. The most frequently requested improvement is to add link resolver capacity. I hope that code4lib users will be able to help. Best regards, David David W. Lawrence, PhD, MPH, Director Center for Injury Prevention Policy and Practice San Diego State University, School of Public Health 6475 Alvarado Road, Suite 105 San Diego, CA 92120 usadavid.lawre...@sdsu.edu V 619 594 1994 F 619 594 1995 Skype: DWL-SDCAwww.CIPPP.org -- www.SafetyLit.org
[CODE4LIB] OpenURL linking but from the content provider's point of view
I have some experience with the library side of link resolver code. However, we want to implement OpenURL hooks on our open access literature database and I can not find where to begin. SafetyLit is a free service of San Diego State University in cooperation with the World Health Organization. We already provide embedded metadata in both COinS and unAPI formats to allow its capture by Mendeley, Papers, Zotero, etc. Over the past few months, I have emailed or talked with many people and read everything I can get my hands on about this but I'm clearly not finding the right people or information sources. Please help me to find references to examples of the code that is required on the literature database server that will enable library link resolvers to recognize the SafetyLit.org metadata and allow appropriate linking to full text. SafetyLit.org receives more than 65,000 unique (non-robot) visitors and the database responds to almost 500,000 search queries every week. The most frequently requested improvement is to add link resolver capacity. I hope that code4lib users will be able to help. Best regards, David David W. Lawrence, PhD, MPH, Director Center for Injury Prevention Policy and Practice San Diego State University, School of Public Health 6475 Alvarado Road, Suite 105 San Diego, CA 92120 usadavid.lawre...@sdsu.edu V 619 594 1994 F 619 594 1995 Skype: DWL-SDCAwww.CIPPP.org -- www.SafetyLit.org
