[Dev] Metadata modelling question
Windhouwer, Menzo
Menzo.Windhouwer at mpi.nl
Mon Feb 15 18:53:37 CET 2016
Hi, Jörgi,
Is the prefix xsi in your record bound to the same namespace URI as in the XSLT?
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance”
Otherwise can you send me/point me to an example CMD record you want to convert.
Best,
Menzo
--
The Language Archive – tla.mpi.nl
From: Jörg Knappen <jknappen at web.de<mailto:jknappen at web.de>>
Date: Monday 15 February 2016 at 18:43
To: Menzo Windhouwer <menzo.windhouwer at mpi.nl<mailto:menzo.windhouwer at mpi.nl>>
Cc: Dieter van Uytvanck <dieter at clarin.eu<mailto:dieter at clarin.eu>>, developers list CLARIN <dev at lists.clarin.eu<mailto:dev at lists.clarin.eu>>
Subject: Aw: Re: [Dev] Metadata modelling question
Hi all,
I am halfway on the way of debugging olac2cmdi.xsl ...
The bug affects all versions of olac2cmdi I have retrieved so far.
What I know by now is:
(a) The template <xsl:template match="dc:contributor"> is really used (and not overridden by the default template)
(b) By replacing the <xsl:if> with an <xsl:choose><xsl:when> construction if found out that the outer if
<xsl:if test="@xsi:type='olac:role'">
evaluates to false even if the input files looks like my example file, i.e.,
<dc:contributor xsi:type="olac:role" olac:code="compiler">Con, Tributor</dc:contributor>
I currently don't understand why it is going wrong here. Ideas?
Greetings from Saarbrücken,
Jörg
Gesendet: Freitag, 12. Februar 2016 um 17:35 Uhr
Von: "Windhouwer, Menzo" <Menzo.Windhouwer at mpi.nl<mailto:Menzo.Windhouwer at mpi.nl>>
An: "Dieter Van Uytvanck" <dieter at clarin.eu<mailto:dieter at clarin.eu>>, "CLARIN EU developers" <dev at lists.clarin.eu<mailto:dev at lists.clarin.eu>>
Betreff: Re: [Dev] Metadata modelling question
Hi Jörg,
If so, you might try
https://github.com/TheLanguageArchive/oai-harvest-manager/blob/master/src/main/resources/olac2cmdi.xsl
which is newer and actively maintained. Fixes (or bug reports ;-) are welcome!
Best,
Menzo
--
The Language Archive – tla.mpi.nl
From: <dev-bounces at lists.clarin.eu> on behalf of Dieter van Uytvanck <dieter at clarin.eu>
Date: Friday 12 February 2016 at 17:28
To: developers list CLARIN <dev at lists.clarin.eu>
Subject: Re: [Dev] Metadata modelling question
Hi Jörg,
are you using https://infra.clarin.eu/cmd/xslt/olac2cmdi.xsl ? Since it should recognize the role (if I look at the code).
If you're using that version there must be a bug in the XSLT, hope you can track it down!
best,
Dieter
On Fri, Feb 12, 2016 at 4:57 PM, "Jörg Knappen" <jknappen at web.de> wrote:
In our current curation project, I got some really nice and fine grained DC metadata with several orles of the
contributors differentiated like this:
<dc:contributor xsi:type="olac:role" olac:code="compiler">Con, Tributor</dc:contributor>
<dc:contributor xsi:type="olac:role" olac:code="depositor">Con, Tributor</dc:contributor>
The olac2cmdi XSLT script just removes the subdivisions of the contributors, leaving only levelled out information
like this:
<OLAC-DcmiTerms>
<contributor>Con, Tributor</contributor>
<contributor>Con, Tributor</contributor>
</OLAC-DcmiTerms>
Thus, some information from the DC metadata is lost in the resulting CMDI.
So, my questions are:
1. Should I care about the information loss? Is the information relevant for further processing in the VLO?
2. If I should care, what should I do?
3. If I don't care, should I remove duplicate lines from the CMDI metadata?
Greetings from Saarbrücken,
Jörg Knappen
_______________________________________________
Dev mailing list
Dev at lists.clarin.eu
https://lists.clarin.eu/cgi-bin/mailman/listinfo/dev
--
Dieter Van Uytvanck
Technical Director CLARIN ERIC
www.clarin.eu<http://www.clarin.eu/> | tel. +31-(0)850091363 | skype: dietervu.mpi
_______________________________________________ Dev mailing list Dev at lists.clarin.eu<mailto:Dev at lists.clarin.eu> https://lists.clarin.eu/cgi-bin/mailman/listinfo/dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clarin.eu/pipermail/dev/attachments/20160215/1b2f7280/attachment-0001.html>
More information about the Dev
mailing list