Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure that language is populated in the CMDI derived from OLAC metadata #3

Open
twagoo opened this issue Oct 16, 2014 · 3 comments
Labels

Comments

@twagoo
Copy link
Member

twagoo commented Oct 16, 2014

See ticket #554 in CLARIN trac:

It matches the pattern
/c:CMD/c:Components//c:OLAC-DcmiTerms/c:subject/@olac-language
defined in facetConcepts.xml​.
...
[..] behaviour of the importer is that these hard-coded patterns will be ignored if the CMDI profile contains at least one element that has a matching conceptlink. This is the case here ("OLAC-DcmiTerms/language", although empty). Therefore normally this attribute is not used to fill the language facet for this profile.
...
[..] convince the creator to include values in the language element in the future.
...
The direct creator of these CMDI's is the harvester, so maybe something can be done there, i.e. fill the 'language' field with the value from the attribute.

(Originally submitted as https://trac.mpi.nl/ticket/4271)

@kjvandelooij
Copy link
Contributor

Original ticket has been closed.

@twagoo
Copy link
Member Author

twagoo commented Dec 15, 2015

This issue still occurs, as is apparent from the values for the language facet in the recently added CoCoON collection. See CLARIN Trac #554 for a relevant discussion.

(It seems that the original ticket was only closed because it was migrated to GitHub)

@twagoo twagoo reopened this Dec 15, 2015
@twagoo
Copy link
Member Author

twagoo commented Dec 15, 2015

Notice that the case might be slightly different (from the one that was fixed primarily in CLARIN Trac #668 in that there actually is a value in these cases, e.g.:

<language olac-language="ita">Italien</language>
<language olac-language="deu">Allemand</language>
<language olac-language="eng">Anglais</language>

Maybe this is more of a mapping/curation issue. To be evaluated...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants