...
2022-2023 Minutes Page, 2020-2021 Minutes Page, 2018-2019 Minutes Page, 2016-2017 Minutes Page, Pre-2016 Minutes Page
| Expand |
|---|
|
ATTENDEES: Wendy, Jon, Oliver, Darren, Dan
APOLOGIES: Flavio 1-Codebook pull request
ok and merged 2-Funding requests (Deadline is 26 of April) Face-to-Face again Infrastructure costs - flag and could suggest it should be a regular budget line; software contingency budget as well as on-going costs 10K last year was infrastructure contingency from which a couple of months of AWS Alliance pays Colectica and this will move to AWS at some point
As part of the move to AWS a bit of work needs to be done to convert from zone file to AWS (route 53) - Dan will write up Admin data meeting - talk to Flavio about meeting next year; funding request
3-Strategic Plan
Looks good - no questions or specific concerns from TC members at meeting 4-Administrative documents
Not ready for discussion 5-CDI submission to TC and production process review
Darren talked with Arofan about RDF URLs and everything is in line Other: CV work is done ready to make the change after confirming a few minor points with ICPSR and the CV group
https://ddicv.ukdataarchive.co.uk/ new format for the CV page (domain to be changed obviously) No ISI proposal but will look at the IAOS conferences coming up
FUTURE:
No Oliver until April 18
No meeting on 11th due to COSMOS conflict |
| Expand |
|---|
|
ATTENDEES: Wendy, Dan, Oliver, Darren, Christophe AGENDA Resolution system CV system RDF hosting/resolution RDF hosting/resolution for CDI (upcoming) is not a dependent on the CESSDA CV version issue being fixed. DB will contact Arofan to clarify CDI RDF serialization’s readiness and double-check required URI patterns for CDI All CVs have unique URIs based on version numbers and are stored in Fuseki default graph. For non-CV products e.g. CDI or DDI4 (that don’t necessarily have versioned URIs) we will create individual graphs for each product.
Codebook pull request review OK and merged 4.0 BETA issues - Comments also added to issue discussion in GitHub Item 8 Changing from internal CV to external could be a Lifecycle 4.1 task Identify those that could be CV Add enumeration documentation to the item type Group ones should probably be taken over by CV group Dan will look through to make sure enumerations are coming through correctly - OWL specs may require URIs for enumerations (this would be an issue for next round of review - how referenced Wendy will look at CV options now. Darren can look at later. This is not urgent. Adding documentation on lists that are currently there. Create notes of what should be added to each README file.
Item 23
Not critical in short term. Good to get multiple eyes on this. Item 36 Should be addressed in 4.0 BETA 2 Add additional notes on previous discussions Group instances to see what could be managed in the same way
FUTURE
Administrative documents (Jon) as available (Jon not on call) |
...