[Tf-curation] Revision for Availability/License controlled vocabulary

[Krister Lindén]

Done. I am not familiar with the BAS licenses. They should be mapped by 
the corresponding CLIC member.
--
Krister

On 9.3.2016 10:41, Ostojic, Davor wrote:
> Dear all,
>
> I added new values to the map. There are only 13 of them.
> When they are mapped I will generate XML map and commit it.
>
> Krister could you map them again?
>
> Best,
> Davor
>
>
>
>> -----Original Message-----
>> From: Krister Lindén [mailto:krister.linden at helsinki.fi]
>> Sent: Tuesday, March 8, 2016 3:51 PM
>> To: Ostojic, Davor <Davor.Ostojic at oeaw.ac.at>; tf-curation at lists.clarin.eu;
>> menzo.windhouwer at meertens.knaw.nl; teckart at informatik.uni-leipzig.de;
>> Dieter Van Uytvanck <dieter at clarin.eu>; Twan Goosen <twan at clarin.eu>;
>> 'Sander Maijers' <sander at clarin.eu>; Penny Labropoulou <penny at ilsp.gr>;
>> Durco, Matej <Matej.Durco at oeaw.ac.at>
>> Cc: hanna.hedeland at uni-hamburg.de
>> Subject: Re: Revision for Availability/License controlled vocabulary
>>
>> Comments in-line:
>>
>> On 8.3.2016 14:52, Ostojic, Davor wrote:
>>> I updated the google spreadsheet [1] with mappings for
>>> availability/license values.
>>
>> I think the Google spreadsheet has been there for quite some time, so I
>> resolved the conflicts.
>>
>> I moved column D to K to make room for added comments in column D.
>>
>>> The main point of confusion are values 'unavailable' and  'undefined'. I
>>> didn't use them in the map because I was unsure if I need to replace RES
>>> with them.
>>
>> Unavailable and undefined all go to UNSPECIFIED.
>>
>>> Another thing is '*'. Did we say that it means 'Other'? In controlled
>>> vocabulary is replaced by 'Other'.
>>
>> = OTHER
>>
>>> During the update I left comments when I was unsure.
>>
>> Resolved.
>>
>>> To summarize, the currently used controlled vocabulary for
>>> availability/license [2] compared to [1] contains some conflicts due to
>>> errors, misunderstandings and confusion
>>>
>>> and it  needs to be revised again by CLARIN's legal experts.
>>
>> I don't know if I qualify as legal expert, but at least I qualify as
>> legal metadata expert.
>>
>>> Could somebody please revise this document? Please pay attention to
>>> fields with comments.
>>
>> Done.
>>
>>> In meanwhile we got around 200 000 new records (vlo on beta has  1 138
>>> 312) and with them new, unmapped values for licenses.
>>
>> Great!
>>
>>> Can somebody (who has access to SOLR's REST API) send me the list of all
>>> values in availability/license indexes: availability, license and
>>> accessInfo and I will update the gsheet with new values.
>>
>> Looking forward to seeing them.
>>
>> --
>> Krister
>>
>>> [1]
>>> https://docs.google.com/spreadsheets/d/1Pf8Jk_P7RaA-7-
>> dj8fcLOKNH5DjprraFEWXgQ3FvVtQ/edit.
>>>
>>> [2]
>>> https://github.com/clarin-eric/VLO/blob/release-3.4/vlo-
>> vocabularies/maps/uniform_maps/LicenseAvailabilityMap.xml
>>>