1 Overview chart. PIDs: talk with EPIC PIDs: MoU or advice. Assessment wave 3. VLO overhaul CMDI 1.2

Transcription

1 Title Centre Committee work plan 2014 Version 2 Author(s) Dieter Van Uytvanck Date Status To be approved Distribution Centre Committee, NCF, BOD ID CE Overview chart PIDs: talk with EPIC PIDs: MoU or advice Assessment wave 3 VLO overhaul CMDI 1.2 FCS specification (basic) FCS Aggregator (basic) FCS specification (advanced) FCS Endpoints (basic) Monitoring all centres Virtual Collection specification Virtual Collection registry Talk with federations New federations join SPF New SPs join SPF Webservices overview Design metadata quality service Curation procedure Prototype metadata quality service 1

2 2 Details 2.1 PIDs: talk with EPIC Summary: Talk with the EPIC consortium about the relation CLARIN- ERIC and EPIC. Requires an overview of the current use of PIDs within all the centres. Responsible: Dieter Van Uytvanck 2.2 PIDs: MoU or advice Summary: After analysing the PID services on offer, make a recommendation towards the CLARIN centers. Might include the need to sign a Memorandum of Understanding with one of the parties (e.g. EPIC). Responsible: Dieter Van Uytvanck, Pavel Straňák (PID taskforce) 2.3 Assessment wave 3 Summary: 1 batch of requests for center assessments, to be sent to the Assessment Committee. In parallel requests to acquire the Data Seal of Approval. Responsible: Lene Offersgaard, Dieter Van Uytvanck 2.4 VLO overhaul Summary: Complete analysis of current code base and reimplementation where necessary, to improve maintainability, documentation, robustness and functionality. Responsible: Twan Goosen (4 PM available, skills required: Java, SOLR, Wicket) 2.5 CMDI version 1.2 Summary: Milestone 1 that contains multiple issues to be addressed, to be released as a follow- up for the current CMDI version (1.1) Responsible: Twan Goosen, Menzo Windhouwer (CMDI taskforce) 2.6 FCS specification (basic) Summary: Formalize the current basic Federated Content Search specifications 2 (and elaborate where necessary, e.g. to allow Boolean operators). 2.7 FCS Aggregator (basic) Summary: extend the current FCS prototype aggregator 3, make it more robust and compliant with the basic FCS specification. If possible integrate some of the advanced FCS specifications D%20Aggregator 2

3 Responsible: developer, preferably to be recruited from a CLARIN centre (4 PM available, skills required: Java, ZK toolkit) 2.8 FCS specification (advanced) Summary: building on the FCS basic specifications, adding more detailed search options for specific types of language resources, at least for POS- tagged text corpora and phonetically annotated corpora (possible other additions, depending on further requirement analysis: lexica, multimodal data, treebanks). 2.9 FCS Endpoints (basic) Summary: At the end of 2013, 10 CLARIN centres have a compliant endpoint available. Make sure these maintain compliancy to the updated basic specification and invite others to setup and endpoint Monitoring all centres Summary: In the previous years (Nagios & Icinga) monitoring has been implemented for some central CLARIN services 4 and for some individual centres. Inventorise what is currently there, streamline it, investigate hosting a computing centre, connect monitoring to the centre registry, integrate it in the CLARIN ERIC website. Responsible: Dieter Van Uytvanck 2.11 Virtual Collection specification Summary: The concept of a virtual collection was loosely defined during the preparatory phase. Now we need to translate the concept into a concrete specification. This includes a few concrete use cases (e.g. citing a virtual collection in a paper, using it to store search results). Responsible: Twan Goosen, Menzo Windhouwer (CMDI taskforce) 2.12 Virtual Collection registry Summary: An alpha version of the VC registry is already available 5. It probably needs a complete reimplementation to make it compliant with the specification document. Responsible: developer, preferably to be recruited from a CLARIN centre (4 PM available, skills required: Java, Wicket) 2.13 Talk with federations Summary: In order to reach all users from the CLARIN ERIC member countries, the SPF needs to be extended with at least the following federations: ACOnet (Austria), Belnet

4 (Belgium), eduid (Czech Republic). Such an operation needs some preparation and close negotiations with the federations in question New federations join SPF Summary: Implementing the extension of the SPF with additional federations, drafting the required document, acquiring the signatures, technical addition New SPs join SPF Summary: At the end of 2013, 11 Service Providers are connected to the Service Provider Federation. Goal is to add new CLARIN Service Providers in the course of 2014, especially the newly setup centres Webservices overview Summary: a written overview with the state of affairs with regards to web services and chaining environments: what is out there, which protocols are used, how to achieve interoperability. Responsible: Webservice taskforce (to be initiated) 2.17 Metadata Curation Summary: Primary concern of this taskforce is to assess (and if possible amend) the quality of the CMD records (i.e. instances), though the quality of the schemas/profiles obviously also plays a role. Towards this goal, within this taskforce, the harvested metadata is checked manually and the found problems are collected and analysed. Furthermore, work is planned on automatic checks of the md records, aiming towards a Metadata Quality Assessement Service, a service that assesses the quality of metadata descriptions (or schemas) based on a number of defined metrics (like availability of resource links, use of recommended data categories and values from controlled vocabularies etc.) Third area is the curation of the values in selected facets/fields/data categories (e.g. organization name) in coordination with the CLAVAS initiative. Responsible: Matej Durco (Metadata quality taskforce) 3 Centralised efforts In accordance with the CLARIN work plan 2014 (CE ), 24 person months will be made available by the ERIC for focused efforts to construct and enhance the technical infrastructure. In this work plan these would be spread as follows: 12 PM for a full- time technical assistant, who will take up continuous tasks such as the SPF administration, maintaining the centre registry, improvement of the 4

5 various web sites and web applications. A separate job advertisement for this position will be distributed. 12 PM for focused code sprints: o 4 PM to refactor the Virtual Language Observatory o 4 PM for advancing the Federated Content Search aggregator o 4 PM to refactor the Virtual Collection Registry 5