> Because, there are 2 possible solutions, and the solution depends on what > makes sense :)
Many thanks for these pointers, that's really helpful, and all makes sense (on first reading anyway) ;-) My first though is that the first approach is probably what we want in this instance, so I take a look at the example and see how far I get! Thanks again, much appreciated. Mike Michael White eLearning Liaison and Development (eLD) Information Services S8, Library University of Stirling Stirling SCOTLAND FK9 4LA Email: michael.wh...@stir.ac.uk Tel: +44 (0) 1786 466877 Fax: +44 (0) 1786 466880 http://www.stir.ac.uk/is/staff/about/teams/aldt/#eld From: João Melo [mailto:jm...@lyncode.com] Sent: 30 October 2013 13:44 To: Michael White Cc: heli...@centrum.sk; dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] DSpace v3 and uketd_dc OAI? Because, there are 2 possible solutions, and the solution depends on what makes sense :) - yeh! It makes sense to make sense. 1. Filtering and Metadata Format tied This solution associates to the Format definition a Filter, so then, for this specific Schema/Format, only a subset of items would be shown. You may want to look at the following example. https://gist.github.com/lyncodev/7232812 Basically, it specifies a Filter within the Format, so then you could query the OAI interface with something like: http://<hostname>:<port>/oai/request?verb=ListRecords&metadataPrefix=uketd_dc 2. Filtering and Metadata Format decoupled This solution decouples the Item Selection phase from the Formatting phase. It requires a 2 steps: 1 - Configure one specific set (or context) to select only Thesis items. 2 - Modify the uketd_dc format accordingly. So then it would be possible to query the OAI interface for thesis items using that format. Something like: http://<hostname>:<port>/oai/request?verb=ListRecords&set=thesis&metadataPrefix=uketd_dc On 30 October 2013 13:07, João Melo <jm...@lyncode.com> wrote: Hi Michael, My understanding is that this is in dc.type - I'm currently liaising with a number of other DSpace users that participate in the EThOS service (the primary consumers of uketd_dc metadata) as there may well be more than one value - I'm hoping though that all the different variations will, at the very least, all contain the word "Thesis", so my first question is to ask if you know if it is possible to use pattern matching to carry out the filtering in xoai.xsl? I am intending to investigate this further, I just haven't got to it yet, but if anyone knows the answer it would be helpful at this stage! Just a simple question. Makes sense to use uketd_dc schema for non-thesis types? On 30 October 2013 11:51, Michael White <michael.wh...@stir.ac.uk> wrote: Hi, > Please, file a new Jira issue for this: With apologies for the delay getting around to it, but I have now done this: https://jira.duraspace.org/i#browse/DS-1740 - this is my first time adding a JIRA ticket, so I hope everything is OK, but feel free to let me know or change anything if not :-) > > > - the output is not limited to only "Theses" > > What metadata field and value(s) in DSpace specifies that the item is a > thesis? My understanding is that this is in dc.type - I'm currently liaising with a number of other DSpace users that participate in the EThOS service (the primary consumers of uketd_dc metadata) as there may well be more than one value - I'm hoping though that all the different variations will, at the very least, all contain the word "Thesis", so my first question is to ask if you know if it is possible to use pattern matching to carry out the filtering in xoai.xsl? I am intending to investigate this further, I just haven't got to it yet, but if anyone knows the answer it would be helpful at this stage! In terms of dc.type - I've also noted an issue with this attribute - it looks to me like any dc.type or dc.type.* attributes are being concatenated into a single dc.type attribute before the data reaches the uketd_dc crosswalk (? Please correct me if I'm wrong!) - I don't think this behaviour is correct in uketd_dc as there are a couple of qualified dc.type attributes that are mapped to their own uketd_dc elements, so I'm hoping that it will be possible to prevent this behaviour when generating uketd_dc OAI metadata (again, not had a chance to look myself yet, but will!)? > Please, provide the mapping of DSpace fields to uketd_dc fields (this will be > an update to uketd_dc.xsl). I am currently working on this specification, which is nearly complete, and liaising with other institutions to ensure that the specified mapping is as generic as possible and so will work for the majority of institutions "out of the box" - alongside this I'm also creating a uketd_dc.xsl crosswalk that implements that specification, and, once complete, hopefully the folk from EThOS will be able to validate the output for us. I'm hoping that all this will only take a couple of weeks to sort out (other work commitments allowing), but that may, of course, be a bit optimistic :-) I hope that covers where I'm currently at and what I'm hoping to achieve, but of course, if anyone has any questions, comments, or concerns (or any pointers for any of the issues noted above), or if you are interested in participating in the specification/testing of this crosswalk (and haven't been in touch so far), then please don't hesitate to get back to me. Regards, Mike Michael White eLearning Liaison and Development (eLD) Information Services S8, Library University of Stirling Stirling SCOTLAND FK9 4LA Email: michael.wh...@stir.ac.uk Tel: +44 (0) 1786 466877 Fax: +44 (0) 1786 466880 http://www.stir.ac.uk/is/staff/about/teams/aldt/#eld -- Thanks, João Melo (My Portfolio) DSpace Department Lyncode: Official website -- The University of Stirling has been ranked in the top 12 of UK universities for graduate employment*. 94% of our 2012 graduates were in work and/or further study within six months of graduation. *The Telegraph The University of Stirling is a charity registered in Scotland, number SC 011159. ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
