TC Meeting Minutes

ATTENDEES: Wendy, Jon, Darren, Flavio, Dan, Oliver, Christophe, Jared, Jeremy

1. AWS and Drupal site interaction and support
   Recap: some sections will move to AWS (specifications) remaining will be moved to wordpress
   Is it wise to split this down the middle and move to 2 sites. This might be difficult to split correctly and to maintain in the future.

--Is it possible to move everything to AWS? How complex might this be to maintain and supervise
--Need to move away from Drupel as it is not supported by ICPSR and want to move it to a vendor
--Fee for moving it over and an annual maintenance amount ($3-4,000 a year)
--Urgency because support for their version of Drupal had gone away, did get year's reprieve
--In the mean time the AWS option arose and discussion of how
--Lots of static content that would just be moved
--Some functinality - bibliography that is maintained in an ongoing basis; posting news etc.
--Happy if it did not got to vendor
--Can we support on-going posting and maintenance
--If not, we can still go to WordPress keeping basic content there and other on AWS

Current view of what goes to AWS:
(1) Content under the following virtual URLs will be moved to the new UMich AWS instance
 https://ddialliance.org/Specification/* - static content
 https://ddialliance.org/products/* - static content
 https://ddialliance.org/learn/resources - single static web page
 https://ddialliance.org/learn/resources/ddi-profiles - single static web page
 https://ddialliance.org/resources/tools - single static web page with filter
o Also move relevant referenced items under https://ddialliance.org/tool/*

o Also move relevant referenced items under https://ddialliance.org/sites/default/files/*
 At the root level under .
o https://ddialliance.org/Tables.dtd - downloadable document

--Clean up even before vendor
--Hidden stuff would not move and Darren's list may include that

--Splitting may have unintended consiquenses such as loss of database functions (publications, examples, etc.)
--Do we need all the functionality that is there (examples etc.) - if we add in with the vendor

--Would the options we are looking support these

--Issue about having to shadow the brand and sync it between 2 sites and with a 3rd party vendor

--What potential costs there would be with backup etc. - there is still need for web support (not completely volunteer)

--It seems to me that we are missing a written target sitemap (whether we have one or two platforms) that would guide the specifics of the migration.

--Could we take a few weeks out to design what we want the site to look like
Include Training Group
We have a current website that needs a spring clean but we have no idea what it should look like
Can we take 4 weeks to say this is where we want to end up (google doc) - we don't have much written down on this at the moment
Drupal to WordPress is somewhat automated there is also a lot of sorting and hand work to make the move.

Lists out the sections and owner groups
Detail gets complex in the products sections
Resources has some sections
What exactly do we have - can we flatten it out?
ACTION:
We should look at what we want rather than just what we have
Create small group to look at this: Jared(co), Jon, Darren (co), Wendy

2. CDI technical review kickoff
   Flavio looked at it
   No draft of production process review issues - get from Arofan (send him a draft of request and list of people we've identified)
   Automation is still lacking so how is that evaluated
   We did write to them some time ago regarding - dig out letter we sent to them and verify all the parts are there
   Asking more information on production process itself; make sure its available
   Jon will look next Friday

3. Funding requests
   see google sheet:

4. Workplan for coming year
   Review workplan for tweaks

5. Updates on feedback for DDI LIFECYCLE V.4.0 BETA
   No only had one piece of feedback from Romain
   BETA 2 would be good to do when we have the ordered flags

ATTENDEES: Wendy, Jon, Darren, Flavio, Christophe, Dan

Pages from Alliance site

• We need to clarify what is moving from the current alliance site before it shifts to WordPress

• The Alliance wants to keep this site a simple as possible and there are currently some pages under LEARN/Resources that have underlying databases

• The majority of content we are looking at is static and is under Products

• Everything that is under Specification is easy but need to determine what needs to be moved

• The real question is about being able to identify specific nodes that can be handled by the remote site (RDF resolution system and CV services on UKDA site plus new DDI Alliance AWS space)

• One possible way is just a lift and shift move all the /Specification

• Landing page on WordPress site and then it sends you off to other system

• What Darren needs is a site map (node list) so he knows what gets moved

Specific questions:

docs.ddialliance.org - what is this intended to provide

• Currently we have a number of official documents associated with specifications that provide access to documentation such as field level documentation and high level documentation

• These are static sets and can be moved

• If it is difficult to tease out the nodes it may be possible to support static content under Products - all of this content is managed by TC

Resources:

• Tools, examples, profiles currently have underlying databases and we would like to retain this functionality

• These items are more in line with the products and it may be optional to move them under the Products umbrella. Learn could still retain a page that would describe and link to these resources

• To accomplish this we need to locate a workable opensource tool to manage search and display of these databases. TC will begin this search

Agency registry:

• DNS integration is being ended in 2025

• Could move to Amazon Route 53 DNS service

ACTION ITEMS:

• Obtain site map (node list)

• Transfer page listing for move to Jared’s spreadsheet

• Determine content that must move to retain or add functionality or to just support easy division of contents for routing

• Clarify who will physically be doing the set up on the AWS configuration

• Identify an open source tool to support access to database content for tools, examples, and profiles

• Determine consequences of moving content to alternate site based on node divisions proposed

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
  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

ATTENDEES: Wendy, Dan, Oliver, Darren, Christophe

AGENDA

Resolution system

CV system

• Access to (am hoping that Oliver will be at TC tomorrow).
  All is in hand

• Misalignment of version numbers in - logged at

• This has been resolved, however there is a problem with the resolving the old version numbers x.x rather than x.x.x

• They will check with CESSDA after talking to Sanda identify where the problem is in terms of inaccurate extensions

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)