I can't check whether Primo supports the qdc metadataPrefix because I forgot my EL docportal credentials. If it does, the problem is now on Primo side so it's best bet for you to work with your EL vendor.
But in general, by the OAI-PMH 2.0 specification, the only mandatory profile is oai_dc, so I would not be surprised if Primo didn't support qdc. In such case I'd take a different approach and map what you need to unqualified fields in a different namespace (called schema in DSpace) than dc. This mapping would be very easy with recent versions of DSpace, but yours is pretty old and I don't think you can do it without writing any code. So the alternatives I see is either update to DSpace 3 (or at the very least to 1.8) or modify your schema to make it flat (yuck) and expose it via oai_dc. To sum up the decision tree: 1) Does Primo support qdc? 1y) see Primo documentation on how to solve the problem 1n) use oai_dc 1n2) are you willing to upgrade to DSpace 3 (or 1.8)? 1n2y) upgrade and edit your oai_dc.xsl to map qdc fields to different oai_dc fields 1n2n) don't upgrade 1n2n3) are you willing to make changes to your schema? 1n2n3y) create a flat schema, you can use multiple namespaces 1n2n3n) customize your OAI Java code to perform the mapping Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ 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
