Hi Kevin & João, I finally got around to creating a JIRA ticket for this bug.
It's at: https://jira.duraspace.org/browse/DS-1479 - Tim On 2/5/2013 1:45 PM, João Melo wrote: > Hi Tim and Kevin, > > as the initial purpose of this new OAI module was (also) to guarantee > 100% backward compatibility, in the following weeks i'll pull for this > change (configurable description). > > PS - It would be better to create a jira issue. > > > On 5 February 2013 18:40, Tim Donohue <[email protected] > <mailto:[email protected]>> wrote: > > Hi Kevin, > > Yes, I misunderstood. I now see what you mean.. > > It looks like, unfortunately, in both DSpace 3.0 and 3.1 this > "Identify" response <description> value is hardcoded. It's actually > not the DSpace source code itself, but rather in the > "com.lyncode.xoai" library that DSpace uses. This library's source > is not distributed with DSpace, but is available on GitHub. > > Here's the exact place where the Description value is hardcoded: > > https://github.com/lyncode/__xoai/blob/master/src/main/__java/com/lyncode/xoai/__dataprovider/OAIDataProvider.__java#L105 > > <https://github.com/lyncode/xoai/blob/master/src/main/java/com/lyncode/xoai/dataprovider/OAIDataProvider.java#L105> > > It's then used later on at: > > https://github.com/lyncode/__xoai/blob/master/src/main/__java/com/lyncode/xoai/__dataprovider/OAIDataProvider.__java#L298 > > <https://github.com/lyncode/xoai/blob/master/src/main/java/com/lyncode/xoai/dataprovider/OAIDataProvider.java#L298> > > I've copied in João Melo from Lyncode, to see if he has any ideas on > how best to either override this default value, or possibly make it > configurable. (It's also possible this could be something we could > try to fix in a future 3.2 release. But, as of yet, we don't have a > 3.2 release scheduled, as we're still waiting to see what additional > bugs / issues may be reported in 3.0 or 3.1) > > - Tim > > > On 2/5/2013 11:35 AM, Kevin Beswick wrote: > > Hi Tim, > > Thanks for the reply. I don't think this is what I'm looking for > though > - as per the requirements of Theses Canada, the description > element must > be included in the OAI-PMH "Identify" response. Currently, the > default > value of the description element that I get when making an > "Identify" > request from the following address - > > http://biblio-dev.laurentian.__ca:8080/dspace-oai/request?__verb=Identify > > <http://biblio-dev.laurentian.ca:8080/dspace-oai/request?verb=Identify> > - is: > > <description> > <XOAIDescription > xmlns="http://www.lyncode.com/__XOAIConfiguration > <http://www.lyncode.com/XOAIConfiguration>">XOAI: > OAI-PMH Java Toolkit</XOAIDescription> > </description> > > Basically I am looking to change the value of that description > element, > or add a second one. From my understanding, the output received from > issuing an "Identify" request does not depend on any particular > crosswalk. > > Thanks, > Kevin > > > On Tue, Feb 5, 2013 at 12:00 PM, Tim Donohue > <[email protected] <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>__>> wrote: > > Hi Kevin, > > To add or change the OAI-PMH elements in the new DSpace 3.x OAI > interface (aka XOAI), you can just modify the proper > "crosswalk". > > XOAI uses a variety of metadataFormat crosswalks which all > exist in: > > [dspace]/config/crosswalks/____oai/metadataFormats/ > > > In this case, it sounds like you just want to add an > element to the > default "oai_dc" metadata format. To do so, you'd modify the > "oai_dc.xsl" in the above folder: > > > https://github.com/DSpace/____DSpace/blob/master/dspace/____config/crosswalks/oai/____metadataFormats/oai_dc.xsl > > <https://github.com/DSpace/__DSpace/blob/master/dspace/__config/crosswalks/oai/__metadataFormats/oai_dc.xsl> > > > > <https://github.com/DSpace/__DSpace/blob/master/dspace/__config/crosswalks/oai/__metadataFormats/oai_dc.xsl > > <https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/metadataFormats/oai_dc.xsl>> > > In this case, you'd likely want to add a new "<dc:decription>" > element into the body of the "<oai_dc:dc>" element > (starting on line > #22). > > If you needed to modify any of the other OAI-PMH metadata > formats, > they all have similar XSLTs in that "metadataFormat/" folder. > > Some additional information regarding how XOAI uses these > various > metadataFormat XSLTs is available at: > https://wiki.duraspace.org/____display/DSDOC3x/OAI+2.0+Server > <https://wiki.duraspace.org/__display/DSDOC3x/OAI+2.0+Server> > > > <https://wiki.duraspace.org/__display/DSDOC3x/OAI+2.0+Server > <https://wiki.duraspace.org/display/DSDOC3x/OAI+2.0+Server>__> > > Let us know if you have any other questions. > > - Tim > > > On 2/5/2013 9:49 AM, Kevin Beswick wrote: > > Hi, > > We are in the process of upgrading from DSpace 1.8.2 -> > 3.0. We > currently participate in a national ETD harvesting > program (Theses > Canada), and one of their requirements in order to > harvest our > content > is that we must include a description element that > contains specific > information in our OAI identify response (detailed here: > > http://www.collectionscanada.____gc.ca/thesescanada/027007-____9200-e.html#a13 > <http://gc.ca/thesescanada/027007-__9200-e.html#a13> > > > <http://www.collectionscanada.__gc.ca/thesescanada/027007-__9200-e.html#a13 > > <http://www.collectionscanada.gc.ca/thesescanada/027007-9200-e.html#a13>>). > > > Prior to 3.0, we achieved this by adding a > configuration entry to > oaicat.properties containing the description information: > > Identify.description.0=<____description>...</description> > > > I'm wondering if there is an easy way to achieve the > same result > using > the new XOAI system in DSpace 3.0, or if someone can > point me in the > right direction? > > Thanks, > Kevin Beswick > Laurentian University > > > > > ------------------------------____----------------------------__--__------------------ > > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-____d2d-feb > <http://p.sf.net/sfu/sophos-__d2d-feb> > <http://p.sf.net/sfu/sophos-__d2d-feb > <http://p.sf.net/sfu/sophos-d2d-feb>> > > > > ___________________________________________________ > DSpace-tech mailing list > [email protected].____net > <mailto:DSpace-tech@lists.__sourceforge.net > <mailto:[email protected]>> > https://lists.sourceforge.net/____lists/listinfo/dspace-tech > <https://lists.sourceforge.net/__lists/listinfo/dspace-tech> > > <https://lists.sourceforge.__net/lists/listinfo/dspace-tech > <https://lists.sourceforge.net/lists/listinfo/dspace-tech>__> > List Etiquette: > > https://wiki.duraspace.org/____display/DSPACE/Mailing+List+____Etiquette > <https://wiki.duraspace.org/__display/DSPACE/Mailing+List+__Etiquette> > > <https://wiki.duraspace.org/__display/DSPACE/Mailing+List+__Etiquette > <https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette>> > > > > > > -- > > Thanks, João Melo (My Portfolio <http://www.lyncode.com/m/jmelo/>) > DSpace Department > *Lyncode*: Official website > <http://www.google.com/url?q=http%3A%2F%2Fwww.lyncode.com%2F&sa=D&sntz=1&usg=AFrqEzdV8iS6rMxflxnn138XReuRfUG3OQ> > > Follow us on Facebook > <http://www.google.com/url?q=http%3A%2F%2Ftwitter.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzeDuT3ZqMW5uVIA8AoxtTtAeiCX3Q> > <http://www.google.com/url?q=http%3A%2F%2Fwww.facebook.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzcWXjHa3gKBGLsNVxktapxkiWDnww> > ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
