 |
 |
Also worth mentioning that in OpenAIRE’s webinar this week, they referenced this: https://gist.github.com/alenkovich/9596992 that extends the vanilla EPrints DC export with a few extra bits of data. These may also be worth a read: https://guidelines.openaire.eu/wiki/OpenAIRE_Guidelines:_For_Literature_repositories#OpenAIRE_Use_of_OAI-DC https://guidelines.openaire.eu/wiki/OpenAIRE_Guidelines:_For_Data_Archives#Metadata_Format (datacite) So, move forward, uptake the new standards, don’t create metadata formats for the sake of it and don’t forget the lowest-common-denominator! Chris’ original message was based in the Library management system / Next-gen catalogue / discovery arena – and some of these systems are still [too] locked down and/or behind the curve WRT metadata formats and interoperability. Cheers, John From: Repositories discussion list [mailto:[log in to unmask]] On Behalf Of Anna Clements Sent: 20 March 2014 14:57 To: [log in to unmask] Subject: Re: DC OAI-PMH Hi all - I would add CERIF to the list of possible formats below. OpenAire are working with eurocris on a CERIF-XML data exchange profile ... see more at http://www.openaire.eu/en/component/content/article/9-news-events/519-public-review-of-the-openaire-guidelines-for-cris-managers-based-on-cerif-xml with Schema at https://guidelines.openaire.eu/wiki/OpenAIRE_Guidelines:_For_CRIS As you will see the data is highly structured so the issue of parsing out elements of a citation does not arise. DC is a highly used legacy format so we need backward compatibility but we also need to look forwards and include CERIF-XML exchange formats for new and improved services ..as OpenAire are doing. Anna ______________________________________________________ Anna Clements | Head of Research Data and Information Services University of St Andrews Library | North Street | St Andrews | KY16 9TR| T:01334 462761 | @AnnaKClements ________________________________ From: Repositories discussion list [[log in to unmask]] on behalf of Rosie, Heather [[log in to unmask]] Sent: 20 March 2014 14:08 To: [log in to unmask]<mailto:[log in to unmask]> Subject: Re: DC OAI-PMH Hi I agree with John’s comments. OAI is not really the problem; if you feel simple DC is insufficient for your needs, then output another format/schema – there are plenty out there (MARC, MODS, RDF, lots of flavours of qDC, including uketd_dc). The only constraint is the serialisation, which must be XML. The problem with exporting a more complex format, however, is that those wanting to use the data may be unfamiliar with it and may not have the workflows in place to process it effectively. Best wishes Heather Heather Rosie EThOS Repository Metadata Manager The British Library [log in to unmask]<mailto:[log in to unmask]> Tel: 01937 546945 From: Repositories discussion list [mailto:[log in to unmask]] On Behalf Of John Salter Sent: 20 March 2014 11:55 To: [log in to unmask]<mailto:[log in to unmask]> Subject: Re: DC OAI-PMH Hi Chris, I wasn’t involved with repositories when these things were being put in place, but have come across similar issues. In my mind, DC is good, as it’s a low barrier, but OAI-PMH is designed to allow other metadata formats to be used when the need arises (e.g. UKETD_DC (EThOS) metadata schema). If Primo can harvest other metadata formats, you could create one that provides the information that you want – but I’m not sure what the capabilities of Primo are. I’ve had some conversations with Sheffield (who also use Primo) in this area, as they didn’t want to present links to content that wasn’t open access. I’m waiting to find out what options there are in Primo for either harvesting specific sets, or using other metadata formats – which may well help solve your problems too. This also provides some good comments on some other issues – based on interpretations of the guidelines: http://core-project.kmi.open.ac.uk/node/31 Cheers, John From: Repositories discussion list [mailto:[log in to unmask]] On Behalf Of Chris Keene Sent: 20 March 2014 11:30 To: [log in to unmask]<mailto:[log in to unmask]> Subject: DC OAI-PMH In the early days of repositories I know a lot of work went in to defining standards for making them inter-operable and to expose their data, notable the OAI initiative. I'm hoping some who were involved in (or who followed) those developments could help enlighten me. For a number of years I've been curious around the reasoning behind adopting Dublin Core via OAI-PMH as the de facto way to harvest and obtain metadata from a repository. (DC isn’t the only format, but it is by far the most common used). To use data exposed by a system - such as a repository - the first thing I would have thought you need to do is interpret the incoming information. When reading information from an IR, the system/script that is importing it needs to establish a number of things: - common bibliographic fields; title, authors, date, publisher, vol/issue, issn/isbn, publication title etc. - DOI - link to IR record - is full text available? if so where, and in what format. - what type of item is it. - Description, citation, subjects etc. While using a common standard (DC) is clearly a good thing. Processing the above can be a challenge, especially as different repository software platforms and versions can present key pieces of information in different ways. This is perhaps made a little harder as there is no field to specify the software/version in the metadata output I'll give a couple examples: To extract the vol/issue/publication title involves looking at all the "dc:identifier" fields, identifying which identifier contains a citation, and then deconstruction the citation to extract the data (and parsing citations is no easy process in itself). To obtain if a record has the full text openly available, ie OA (with an Eprints system): Check to see if there is a dc:format - if it exists there is a file associated with the record. But to check it is OA, and not locked down (which is quite common) find the dc:identifier which starts with the same domain name as the OAI interface, presume it is a link to the full text, try and access it, if you succeed (http status code 200) then it is OA. Though if you only have the metadata to work with and can't try and retrieve the URL while processing the record, you obviously can’t do this. Dspace provides quite different data via OAI-PMH so this method would not work. The reason I bring this up now is that I'm currently trying to improve how our repository records are displayed in our discovery system (Primo, from Ex Libris), the metadata is currently so poor we have hidden them. A key concept of these systems is that they know which items the user has access to (across all the library's collections and subscriptions), and by default only returns those which the user can access. While Primo has quite a complex system for configuring how records are imported, it doesn't extend to the sort of logic described above. So from my specific use case (and other dabbling in this area) the data provided by OAI-PMH DC seems difficult to work with. I'd be interesting to learn a bit of the history of the thinking of how this approach cam about, and whether there are better approaches in processing the data than those I have described here. Regards, and thanks in advance to any insights Chris For reference here are two examples (you may find using Firefox, view source, works best) Eprints (record with a file attached, but not OA) http://sro.sussex.ac.uk/47853/ oai http://sro.sussex.ac.uk/cgi/oai2?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:sro.sussex.ac.uk:47853 Dspace https://www.era.lib.ed.ac.uk/handle/1842/164 http://www.era.lib.ed.ac.uk/dspace-oai/request?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:www.era.lib.ed.ac.uk:1842/164 Chris Keene - Technical Development Manager, University of Sussex Library Contact: http://www.sussex.ac.uk/profiles/150000 ****************************************************************************************************************** Experience the British Library online at www.bl.uk<http://www.bl.uk/> The British Library’s latest Annual Report and Accounts : www.bl.uk/aboutus/annrep/index.html<http://www.bl.uk/aboutus/annrep/index.html> Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook<http://www.bl.uk/adoptabook> The Library's St Pancras site is WiFi - enabled ***************************************************************************************************************** The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the [log in to unmask]<mailto:[log in to unmask]> : The contents of this e-mail must not be disclosed or copied without the sender's consent. The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author. ***************************************************************************************************************** Think before you print