Page Comparison

ATTENDEES: Wendy, Oliver, Jeremy, Dan, Darren, Flavio

Quick recap

Wendy provided an update on the CDI status and discussed two issues raised by Jeremy, one related to the automated pipeline setup (CDI_100) and the other concerning XML schemas (CDI-101). The team also discussed the challenges of publishing multiple incompatible XML schemas and the status of issues related to the package. Lastly, they discussed the TC management of the Alliance website, the synchronization protocol, and the ongoing project, emphasizing the need for updates on assignments and testing email templates and mail shot functionality.

Next steps

• Flavio to update the CDI issue tracker to clarify the status of all issues for the technical committee's review.

• Darren and Oliver to review and refine the website management roles and responsibilities document.

• Wendy to create documentation on how to make content entry changes to maintain consistency with templates.

• Darren to email Sanda about the preferred placement of concept URIs in the CV tables and coordinate with Oliver on implementation.

Summary

CDI Status Update and Issue Resolution

Wendy provided an update on the CDI status, mentioning that they are still expecting a submission by tomorrow. She also discussed two issues that Jeremy had raised, one related to the automated pipeline setup and the other concerning XML schemas. A comment was added to CDI-101.

Discussing XML Schema Management and Automation

Wendy, Jeremy, and Dan discussed the challenges of publishing multiple incompatible XML schemas. They agreed on publishing a single canonical schema in the package, with additional schemas separated and using different namespaces. Wendy suggested adding a comment reflecting this decision. The team plans to automate the process with a continuous integration pipeline triggered by publication from their modeling tool. Oliver was identified as the contact for the pipeline work. The package delivery is intended for tomorrow, though some details still need to be confirmed with others. The team aims to fully automate the schema management and publication process. Given we always said the spec was tool-agnostic, Jeremy and Flavio see no reason for publishing a second XML schema developed specifically for tools, even if they are very common. We recommend the second schema be made available at a later date as an add-on to the spec.

Discussing Package Issues and Jira Tracker

Wendy and Jeremy discussed the status of issues related to the package. Jeremy expressed concern about the number of open issues and the lack of a plan to address them before publishing. Wendy clarified that Flavio hadn't had a chance to update the status of these issues. Dan provided information that Flavio had fixed about 20 of the issues. Wendy suggested updating the Jira tracker to clarify what's been finished and what's future work. The team agreed on the importance of having an up-to-date issue tracker for the review process.

CDI Webinar Announcement

Wendy noted the text for the announcement of the CDI webinar focused on the upcoming voting process and asked for comments on the draft webinar details.

Technical Committee Website Management and Roles

Wendy discussed the management of the Alliance's website, focusing on content distribution, administrative roles, and website performance. She proposed a division of roles between Darren and Oliver, with Darren handling HTML, branding, and styling, and Oliver managing database-driven content and file management. Wendy also suggested the creation of an archivist role to ensure related pages receive necessary changes. Darren agreed to review the content management document and make necessary clarifications.

Synchronization Protocol and Content Updates Discussion

Wendy discussed the synchronization protocol and the process of updating content between Drupal and HubSpot. She mentioned that she is recording changes and keeping a folder of content changes. Wendy also noted that to provide Jared with access, Jon would have to lose his access to Drupal, but this might not be a good idea during the development period. She mentioned that new documents will be added using the HubSpot system, which should put them in the same place as those that were transferred from Drupal. Wendy also raised a question about additions and changes to the databases, which Oliver was asked to provide answers for.

Project Updates, Testing, and Webinar Planning

Wendy discussed the ongoing project, emphasizing the need for updates on assignments and inquired about the status of testing email templates and mail shot functionality. Darren confirmed that they had tested mail shots but needed a more real-world situation. Wendy also questioned the timeline for the project. Darren agreed that the flip over should happen after Eddie due to unresolved issues with the new website. She also emphasized the importance of reviewing the deadline dates on the shared spreadsheet. She is prioritizing the entry process document to ensure consistency in entry procedures before involving Jared.

Column Placement Discussion in Controlled Vocabulary HTML Table

Wendy and Darren discussed the possibility of adding concept URIs to the HTML pages, with Darren suggesting that it would be beneficial for their developer to insert another column in the tables to hold the concept URI. The team discussed the placement of a new column in a table. Wendy suggested that the column, which contains the concept URI, could be placed below the concept label in a different font or color to save space. However, she also noted that the column should be placed in the before the label column to avoid implying a change between languages. Oliver suggested placing the column in the second column to avoid blurring with the hierarchical indent. The team agreed to ask Sanda for her preference on the placement of the column.

Finalizing Feature Changes and Upcoming Tasks

Wendy and Darren discussed the final changes needed to make a feature live. Darren mentioned that a redirection was required, which was a simple task. Wendy emphasized the importance of making the concept URI feature prominent to encourage its use. For the following week, Darren didn't have specific topics, but Wendy mentioned the need to address the CDI submission. She also mentioned that she was working on high-level documentation for the Codebook. Dan was reminded to let Wendy know when the Beta 2 changes were completed, and to review the documents for any necessary comments or changes.

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