Re: [Dspace-tech] QDC Crosswalk and OAI 2.0

2013-10-21 Thread kotsomit
I have provided an XSL transformation which makes an exhaustive map of the DSpace AP elements to dcterms (a la the old qdc.properties). In brief: - additional elements are now exported - language tags are now exported - map everything under the dcterms namespace (rather than mixing dc with

Re: [Dspace-tech] QDC Crosswalk and OAI 2.0

2013-08-02 Thread Muilwijk, M. (Marina)
Dimitrios, you can get any output you want by editing (or adding) an .xsl file. To get the same output as the old QDC crosswalk, you can look at qdc.xsl. It's not really a simple way, but if you have some experience with XSLT, it's not difficult. More on the metadata formats can be found at

Re: [Dspace-tech] QDC Crosswalk and OAI 2.0

2013-08-02 Thread helix84
On Thu, Aug 1, 2013 at 5:06 PM, kotsomit kotso...@hpclab.ceid.upatras.gr wrote: However, what is the basis schema for this metadata? As far as I have seen it is a proprietary schema by Lyncode called “xoai”. Hi Dimitrios, xoai| is just an internal format. You can see any record in this format,

[Dspace-tech] QDC Crosswalk and OAI 2.0

2013-08-01 Thread kotsomit
[reposted at dspace-tech which might be more appropriate] I understand that with the new OAI 2.0 in DSpace 3.x the crosswalk plugins are no longer used for OAI output, e.g. enabling the QDC crosswalk and modifying the qdc.properties file has no effect. Instead, there is a series of .xsl files