= Joint CMDI & Curation taskforces meeting 2017-05-17 =
----

* What?
 * CMDI 1.2 best practices
* Who?
 * Members of the [[Taskforces/CMDI|CMDI]] or the [[Taskforces/Curation|Curation]] taskforces and other people involved/interested in the specification of best practices for CMDI
* When? 
 * 17 May 2017, 13.30 - 17.00 CEST (on basis of [https://www.clarin.eu/event/2017/centre-meeting centre meeting program])
* Where?
 * [https://www.uu.nl/en/achter-sint-pieter-200 Achter Sint Pieter 200, Utrecht (NL)]

== Documents ==
 - [https://trac.clarin.eu/wiki/Taskforces/CMDI/Meeting20170118#Documents existing (draft) best practices documents]
 - [https://docs.google.com/document/d/1Cr_UqoQFPLt3ucovUuCxne7XVSMZ4awUupev2bTzewc/edit?usp=sharing draft CMDI Best Practices doc] on Google Docs 
 - [attachment:CAC17-CMDI-BP-20170508.pdf CAC 2017 submission "Component Metadata Infrastructure Best Practices for CLARIN"]
== Preparation ==

 * [Menzo] finish the `General XML`, `The envelope` sections
 * [Oddrun] align the `Resource Relations` section with the approach of other sections
 * [Susanne] work on prose for the `The Component Section` section
 * [all] add best practices suggestions/comments to the other sections


== Agenda ==

1. Agenda
1. Status update (10 minutes)
  * CMDI
  * CLAVAS
  * Curation
1. B-centre assesment: requirement for usage of public profiles
1. Addition of concept links to production profiles/components
1. Best practices

== Notes ==
=== Status update ===
    1. CMDI
        * Best practices, !CompReg implemented, CLAVAS getting in production status
        * Status support at centres: Leipzig providing; Meertens work on FLAT, CMDI 1.2 is not high priority however so will be 1.1 initially (also MPI); ACDH will be providing CMDI 1.2 at time of assessment; META-SHARE should be combined effort, no initiative yet; EURAC has intention to start off with CMDI 1.2; to be discussed with D-Space development team
    2. CLAVAS
        * Running at Meertens, now embedded in CMDI (1.2). Being upgraded to OpenSKOS 2, some technical difficulties causing a delay.
        * CCR Data stays as it is; old CLAVAS vocabularies are forgotten. CLAVAS instance now runs at a CLARIN host - to be replaced by Meertens instance. Then additional vocabularies can be added.
        * Licences: Oddrun has a licence vocabulary (140 licences). To be merged/aligned with curation TF's licence vocabulary? 
            * Matej: would be nice, who is willing? Who is in charge?
            * `TODO` Arrange a follow-up vidconf with Oddrun. Also checking with/involving CLIC ('''Matej''')
        * Organisations: still work in progress (Menzo)
        * Mime type inventory: import from IANA registry
            * Extension of 'Subtypes', e.g. TEI, could be included in CLAVAS. Also plain text vs linguistically annotated ASCII
    3. Curation
        * Davor left, now replaced by Wolfgang.
        * The curation module is back up.
        * Looked at DTA records from BBAW, lower score than expected.
            * https://trac.clarin.eu/ticket/1009

===  Formulation of requirement ===
"The CMDI profiles, that a centre uses, have to be public to be accepted in assessment. As mentioned above, in the current version of CMDI, public profiles cannot get updates of links to CCR. We hope that the metadata curation taskforce looks into this dilemma." ([https://office.clarin.eu/v/CE-2017-1015-centre-assessments-round8-to_CAC_v1_1.docx document])

We propose the following rephrased sentence: "The CMDI profiles, that a centre uses for their published metadata, have to be public, with preferably status production but draft or deprecated are acceptable, to be accepted in assessment."

`TODO` Proposed this rephrased sentence to the SCCTC (through Lene?)

=== Adding of concept links after production? ===
    1. Option: allow this to be done by the owner (only add, not update)
    2. Preferred option: compreg admins remains the 'doorkeeper'
        * `TODO`: propose a note gets added to the requirement document stating that the !CompReg admin (registry manager?) can be contacted to get this done.

=== CMDI best practices ===
    * Order based on priority?
    * Consider moving the workflow subsection up, as the first subsection within their sections?