TC Meeting Minutes

ATTENDEES: Wendy, Oliver, Dan, Jon
REGRETS: Darren, Flavio

Quick recap

Wendy, Dan, and others discussed the status of website updates, the publication process for CDI, and the potential shift of published packages from Bitbucket to Github. They also reviewed the roles and responsibilities of the management group, the progress of the technical committee's work, and the need for clearer application profiles. The team agreed to revisit these issues in future meetings and explore alternative methods for XML usage.

Next steps

• Dan to contact Achim regarding the issue with creating the package for CDI publication and provide instructions.

• Wendy to have Achim write to Dan (copying Oliver) explaining the specific issue he's having with creating the package.

• TC to review and finalize the website review and management documents shared by Wendy.
  Review process
  https://docs.google.com/document/d/1ByEfdJDmSC1rSCdjJ7gNWBzar9DNShTiQ6q0-a2L-oc/edit?usp=sharing

• TC to work with Jared on forming the management group for the website (this would be under the EB).
  Web management
  https://docs.google.com/document/d/1q3c0Gzfqys5waAnwWFJORY99n6fxoQ2SLenIGx0bEPg/edit?usp=sharing

• Technical Committee members to review and provide feedback on the new technical infrastructure page on the website.
  https://ddi-alliance.atlassian.net/l/cp/P4Cx6ct2

• Dan to present examples of profile tasks using Dublin Core application profiles at the next meeting.

• Jon to prepare notes and thoughts on questionnaire profile validation for discussion at the next meeting.

• Wendy to inform Jared about using tomorrow as the official publication date for the website and start negotiations for the announcement.

Summary

Website Update and Package Publication

Wendy discusses the status of the website update and the publication process for CDI. She mentions that some concerns raised by Jared have been addressed, including the maintenance of the tools list.

CDI Publication

CDI issues for TC:

• Publication of package - how to produce the download package in github

• Where are publication packages being placed

• Use GitHub releases - upload assests as a release and includes a source as part of a release as well

• Still need a zip file with a full package

• This is the final part of the full pipeline - a deliverable asset to be stored

• Produce a complete download package, partial download package for the field-level documentation folder and sub-folders

• ACTION: Have Achim provide details on the problem he is having to Dan cc Oliver and Wendy

• CDI link updates later today

• Arofan will go through the pages

• Dan and Wendy discuss the issue of creating a package for publication, as Achim is unsure how to produce it. Wendy asks Dan to follow up with Achim to clarify the problem and provide instructions. They also discuss shifting the storage of published packages from Bitbucket to Github, with Dan suggesting the use of Github releases for this purpose.

Website Management

Wendy shared a document for review and management of the website, outlining the roles and responsibilities of the management group, including a technical representative, user interface specialist, content specialist, and archivist. There was some confusion about the file management responsibilities, with Dan confirming he set it up and Oliver expressing unfamiliarity with it. The next steps include getting the management group together and working with Jared and Jon to formally organize the group.

Technical Committee Progress and Feedback

Wendy discussed the progress of the technical committee's work, including the creation of a technical infrastructure page and the ongoing editing of guidelines. She emphasized the need for feedback on the new site and the importance of understanding the technical infrastructure. Wendy also mentioned the upcoming discussion on the contents and organization of the http://docs.ddialliance.org . Jon agreed with Wendy's points, highlighting the need for more control over content and the ability to make changes. Dan suggested discussing the profile task again to get a status update.

Clarifying Application Profiles and Validation

Dan and Wendy discussed the need for clearer application profiles, particularly for the Dublin Core and CESDA. They agreed that the current XML usage was difficult to use and suggested exploring alternative methods. They also discussed the importance of having a list of available profiles for different implementations. Jon added that the profile should include conditional elements and a validation process, especially for content validation. The team agreed to revisit these issues in future meetings.

NEXT WEEK'S AGENDA

• http://docs.ddialliance.org discussion

• DDI-Lifecycle Profile task - Dublin Core application profile for CESSDA (Dan will provide some examples)

  • What do we want to suggest for profiles - content groups are interested

  • Determine scope of profile

  • Validation of content against profile

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

Agenda:

• Website

• DDI-CDI publication

• DDI-SDMX mapping

• Variable cascade

Quick recap

The team discussed the progress of their website project, focusing on addressing issues raised by Jared and the need for a Javascript developer. They also discussed the mapping between DDI and SDMX standards, the need for better coordination across different communities, and the establishment of a lifecycle committee and a codebook committee for content iterations. Lastly, they discussed agenda items for February: http://docs.ddialliance.org , the upcoming establishment of a lifecycle and codebook committees, and the potential for future changes to their web page project.

Next steps

• Darren to send a status update on the website to Wendy and Jared by the end of tomorrow.

• Darren to work with a JavaScript developer to implement filtering functionality for publications and tools pages early next week.

• Wendy to change the stubs for lifecycle and CDI to follow the same naming convention as other versions.

• Wendy to set up HTML pages for CDI version 1.0 within an hour after the meeting.

• Darren to set up routing for CDI URLs after the meeting.

• Wendy to send a reminder to the CDI group about their commitment to the production pipeline automation.

• Flavio to check on existing mappings between Lifecycle and SDMX.

• Technical Committee to consider creating a temporary working group under the Scientific Board for major mappings across DDI products.

• Technical Committee to discuss the variable cascade issue and determine who should address it.

• Technical Committee to prepare an agenda item for the first meeting in February to plan next steps for mapping activities.

• Wendy to focus on Codebook after the website and CDI are completed.

• Technical Committee to review and update the technical infrastructure documentation in Confluence.

• John to provide clarity on what will be on docs.ddialiance.org and the timelines for implementation.

• Scientific Board to prepare for upcoming elections, including at least one open position.

Summary

Website Progress and Future Improvements

Wendy led a discussion about the progress of the website, with a focus on addressing issues raised by Jared. Darren confirmed that he had made temporary fixes to the membership page, but acknowledged the need for a more permanent solution. The team also discussed the need for a Javascript developer to work on the publications and tools page. Wendy suggested that someone with Javascript knowledge would be a valuable addition to the team. Additionally, Wendy noted a discrepancy in the naming convention for the lifecycle version pages and decided to change it to align with the rest of the website.

Web Page Project Progress and Testing

Wendy, Darren, Flavio, and Oliver discussed the progress of their web page project, focusing on the redirection of pages, the need for a status update by the end of the next day, and the potential for future changes such as separating the 'getting started' section and moving the glossary to the product section. They also discussed the need for testing URLs before publication and the need for field-level documentation. Flavio mentioned the need for an update on the pipeline commitment.

DDI and SDMX Mapping Discussion

Wendy and Flavio discuss mapping between DDI and SDMX standards. Wendy mentions there is already some existing mapping between lifecycle and SDMX that needs updating. She will locate that previous work. Wendy also notes that codebook has an n-cube, so that should be considered. The mapping activity originated in the UNECE's Modernstats Supporting Standards group, where it remains an ongoing effort for this year.

Improving Data Integration and Coordination

Flavio and Wendy discussed the need for better coordination and alignment across different communities, particularly in terms of data integration and mapping. They agreed on the importance of understanding existing mappings and lifecycles, and the need for a group to oversee these processes. Wendy suggested the creation of a temporary working group under the scientific board to handle these tasks. They also discussed the variable cascade and the need for consistency across different products. Dan mentioned that the RDF Equivalence group would be working on similar issues. The team agreed to plot out their next focus areas and ensure that important tasks do not get dropped.

Transition to Docs and Committee Roles

Wendy and Darren discussed the need for more clarity on the transition to http://docs.ddialliance.org , with Darren expressing a desire for specific timelines. Wendy agreed to prioritize this issue and mentioned that Jon would be more available for the discussion in the near future. Wendy also brought up the upcoming establishment of a lifecycle committee and a codebook committee for content iterations. Furthermore, Wendy mentioned that there would be at least one open position on the scientific board, suggesting a competitive election process. Ingo was noted to be stepping down from the Scientific Board to focus on tools and hackathons.

Future meeting agenda items:

• http://docs.ddialliance.org organization and content

• Codebook v2.6 publication

• Lifecycle v4.0 publication

• Codebook WG

• Lifecycle WG

• Mapping work

ATTENDEES: Wendy, Oliver, Darren, Dan, Flavio

REGRETS: Jon

AGENDA:

• DDI Newsletter

• DDI-CDI Publication

• Website work

• Website management group

Quick recap

The team discussed the DDI CDI publication, website coordination, and the formation of a future web management group. They also addressed the need for generating XML schema documentation, the placement of certain resources on the website, and the process of editing guidelines for the website. Lastly, they outlined the next steps for the project, including writing up more detailed terminology and providing information to CDI by the next day.

Next steps

• Darren to update the document with URL clarifications and send it to Wendy for review before sending to Achim.

• Wendy to create a Google Doc of Darren's document and link it to the meeting minutes.

• Darren to complete the database-driven pages for the website.

• Darren to email Jared about obtaining newsletter data if not found in the Drupal backup.

• Wendy to write up a more detailed proposal for the future web management group and circulate it to Jon, Jared, and Oliver.

• Darren to add information on directional information and editing guidelines for database pages to the web editing guidelines document.

• Wendy to continue adding screenshots to the web editing guidelines document.

• Technical Committee to consider content for the newsletter announcement regarding the website or other committee activities.

• Darren and Wendy to plan a webinar to introduce the new website to users once it's up and running.

DDI CDI Publication and Website Coordination

Wendy led the meeting, discussing the DDI CDI publication, website coordination, and the future web management group. She announced that the newsletter deadline had been extended to the 31st to accommodate the announcement of both the website and CDI publication. Flavio mentioned minor model corrections that needed to be made, which he planned to discuss with Arafan later. Wendy also discussed the need to modify web pages for CDI and move information into the overview. Darren's email was shared, and he clarified that most of the issues were straightforward, with many options for setting up redirects. The team agreed to provide any necessary information to the CDI team by the end of the day or the following day at the latest.

Canonical URL for Model Documentation

Darren discussed the need for a canonical URL for the model field level documentation, suggesting it could be either docs.ddilliance.org or a consistent pattern with specification/ddi-cdi/1.0/model/field level documentation that redirects to docs.ddillance.org. Wendy pointed out the need for a version number in the URL. Dan suggested including the XML schema documentation generated by DocFlex on the docs.ddiliance.org site, following a similar pattern to other products. Darren agreed, noting that the XML schema documentation hasn't been generated yet as it's been focused on the model.

DECISION: Keep the specification path as the canonical Specification/DDI-CDI/1.0/model/field-level-documentation but house in docs.ddidocumentation.org

XML Schema Documentation and Tool Status

Darren, Wendy, and Dan discussed the need for generating XML schema documentation, which is currently not being done. They agreed to bring this up with Jon in the next meeting. They also discussed the status of the tool used for generating this documentation. Darren mentioned that he had set up redirects on HubSpot for field level documentation and had a few more to do. The team also discussed the possibility of moving XSD artifacts to docs.ddilliance.org, but decided to discuss this further in a future meeting.

System Interaction and Development Management

Wendy discussed the need for higher level instructions on how people can interact with the system and manage development things. This was raised in the CDI meeting as is on their future agenda She suggested a meeting with the CDI and Technical Committee to ensure a consistent approach across the product. Darren confirmed that the XSD files are in Hubspot and the redirects are set up. He also asked Dan to deploy the package onto http://docs.ddialliance.org once it's ready. There was a discussion about the path for the DDI-CDI and the need to update the path on the docs site. Lastly, Darren and Wendy discussed the placement of the Turtle and JSON-LD packages, confirming that they should be hosted under the RDF URL.

Project Naming Convention and Website Cleanup

Wendy and Darren discussed the need provide Arofan and Achim with a clear list of URL, date, and version changes needed in the CDI publication package. Darren will provide a firm list of changes and URLs for the new version. Wendy will review before sending to Achim. Wendy will manage the standard updates to the web pages required for new publication.

Website Editing Guidelines and Resources

Wendy discussed the process of editing guidelines for a website, focusing on the setup of nesting patterns and the use of dropdowns. She raised the question of the inconsistent use of 2nd tier nesting on the drop down menus. Darren agreed that this was a content review issue. Wendy also mentioned the creation of a Confluence page of the Technical Committee, where she plans to include information about the website's technical infrastructure. She is currently working on the web editing guidelines and is open to feedback and questions.

Website Updates and Newsletter Management

Wendy discusses updating internal document links, related content, and database content on the new website. Darren provides updates on correcting file links and working on data-driven pages. They discuss handling newsletters, with Dan sharing an archival link to past newsletter PDFs and pages. Wendy suggests having submission forms for examples and tools that get reviewed before publishing to improve the process over the previous approach.

Location of old web pages to view past layout for verification:
https://web.archive.org/web/20241217184156/https://ddialliance.org/publications/newsletters

Forming Web Management Group

Wendy discussed the formation of a future web management group, which would consist of 4 to 5 people, including two editors for administrative and product content. The group would also include a technical support person and individuals with web layout and marketing skills. Wendy emphasized the importance of maintaining close ties with marketing and training. She also mentioned the need for an archivist to ensure consistency and alignment across different sections of the website. Additional people, volunteered or paid, could be added for specific activities such as a usage assessment. Darren agreed with Wendy's proposal, and the group decided to move forward with the plan. The web management group would be a working group of the Executive Board. Wendy will write this up in more detail and discuss with Jared, Jon, and Oliver. TC can review again when something is decided by this group.

Future items

Darren was tasked with providing information to CDI by the next day and adding directional information to the databases. Wendy has created a centralized place for web and technical infrastructure guidelines and the importance of maintaining consistency. The team discussed the timeline for CDI automation, with the first deadline in March. Wendy also reminded the team to provide suggestions for the website and newsletter. Lastly, Darren suggested a webinar to introduce the website to users once it's ready.

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

Quick recap

The team discussed updates and tasks related to the website and DDI, including the progress of updating external URL links and the need for clear instructions for editing and updating the databases. They also discussed the need to clean up and reorganize the file structure for their project, and the progress of the DDI-Lifecycle v4.0 Beta 3 revie. Lastly, they initiated a discussion about future agenda items and encouraged team members to communicate their needs for upcoming meetings.

Next steps

• 
  Darren to continue updating website pages and links, aiming to finish by Monday morning.

• Oliver to be available tomorrow for Darren to check data-driven pages.

• Wendy to work on finishing the draft instructions for editing the website this week.

• Wendy to create a new subsection under the TC page for website management documentation.

• Darren to email Wendy tomorrow with his understanding of where CDI files are currently located and where they should go.

• Wendy to move the CDI product page back to "developing products" section until publication.

• Dan to send a reminder on January 15th for additional feedback on Beta 3.

• Dan to implement JSON, XML, and RDF versions of Beta 3 in the next couple of months.

• Dan to conduct round-trip testing between 3.3 and 4.0 versions.

• TC to follow up on CDI commitments for automation processes, particularly first quarter deadlines.

• Dan to continue work on representing profiles across different DDI Lifecycle representations.

• Dan to write up different ways to make profiles in various serializations for community feedback.

Summary

Website Updates and DDI Tasks

Wendy and Darren discussed updates and tasks related to the website and DDI. Darren mentioned that he was working on serving the website on SSL and expected to complete this by Monday. He also planned to check the rest of the data-driven pages the following day, and needed Wendy's assistance in review. Oliver was also expected to contribute to the project.

Website Updates and Documentation Plans

Darren and Wendy discussed the progress of updating external URL links to internal page links on the website. Darren agreed to continue working on this task and mentioned the need for a more detailed conversation about docs.ddilliance.org. Wendy agreed to include this on a future agenda. They also discussed the need for clear instructions for editing and updating the databases, which Wendy agreed to work on. Darren suggested documenting how the data modules work, and Wendy proposed creating a new subsection under the website management page for technical documentation. No other issues or questions were raised.

Project File Structure and Documentation

Wendy, Jon, and Darren discussed the need to clean up and reorganize the file structure for "http://docs.ddialliance.org ". Darren agreed to go through the files one by one, as most were configured as URLs rather than file links. Jon offered to help with the process. They also discussed the need to update the XML schema and RDF resolution pieces before publishing. Darren agreed to draft an email to Wendy to clarify his understanding of the project's current state and future plans. They also discussed the need to move the field level documentation for CDI to the correct location on Docs.ddi.

Beta 3 Review Progress and Implementation

Wendy and Dan discussed the progress of Beta 3 review. Dan mentioned that Vincent had reviewed the updated Json schema and found it to fix the issues from the DDI Hackathon. They also discussed the need for more feedback and the importance of implementation in Python. Dan mentioned that they would implement the Json, Xml, and Rdf versions in the next couple of months and conduct round trip testing between versions 3.3 and 4.0.

Future Agenda Items and Meeting Adjustments

Wendy suggested following up on the commitments made by CDI regarding automation processes. Dan also discussed his work on representing profiles across different representations and the need for more examples and proposals. He suggested writing a document about different ways to make profiles in different serializations and sending it out for comment. Wendy agreed that this could be a good first step towards creating supplementary publications to support the use of the DDI.

Wendy initiated a discussion about future agenda items, encouraging team members to communicate their needs for upcoming meetings. Flavio and Jon participated in the conversation, with Flavio joking about not invading Canada. Oliver requested a shift in a certain aspect, which Wendy agreed to. The conversation ended with Dan expressing gratitude and Wendy turning off the AI companion.

ATTENDEES: Wendy, Jon, Dan, Darren, Flavio
REGRETS: Oliver

Agenda: Update on Website work

Issue for schema validation
Example:
https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/instance.xsd

https://app-eu1.hubspot.com/user-guide/144531336
CNAME record is now correct:
DNS Propagation Checker - Global DNS Checker Tool

Quick recap
The team discussed the ongoing issues with the website transfer to Hubspot, including DNS transfer problems and the need for setting up redirections for the specification URLs. They also discussed the potential consequences of rolling back the changes and the need to sort out publication plans for the CDI in January.

Next steps

• Darren to resolve DNS transfer issues with Candice within the next couple of hours.

• Darren to work on database-driven summary listing and hyperlink generation for individual record pages over the Christmas holidays.

• Darren to set up redirections for specification URLs to the correct locations on docs.ddalliance.org.

• Wendy to finalize and send the instructions for editing to Darren for review.

• Darren to contact Hubspot regarding the round-robin DNS issue if it persists.

• Wendy to send out a note on the user list if the site is expected to be down over the holidays due to transfer issues.

• Technical team to determine the appropriate locations for CDI publication and documentation by the January meeting.

• Wendy to coordinate with the team for the CDI publication in January, ensuring correct links and placements.

SUMMARY

DNS Transfer and SSL Certificate Issues

Wendy initiated a discussion about the status of the website, specifically the DNS transfer to HubSpot. Darren reported that the transfer was initiated the previous day, but some records were not yet picked up. He mentioned that Hubspot would automatically provision an SSL certificate once it was satisfied with all the DNS records. Darren also mentioned an issue with a CNAME record not being picked up by the Google Admin tools or any DNS tools, and he planned to discuss this with Candice and Jason, who are responsible for maintaining the zone file.

Hubspot Documentation and Redirection Issues

Wendy, Darren, and Flavio discussed ongoing issues with the documentation in HubSpot. Darren explained that he had found a solution to the problem and was available to work on it over the Christmas holidays. They also discussed the need for setting up redirections for the specification URLs to the correct location, with Darren offering to upload the necessary files into the correct folders on Hubspot. Dan confirmed that the generated documentation was currently the only thing added, and that the actual schemas would need to be put somewhere.

Website Transfer and DNS Discussion

Wendy and Darren discussed the process of moving their website to a new location. Wendy asked about the need to switch login addresses, to which Darren responded that the admin console URL would still be used for editing and content publishing. He also mentioned that he would have a better understanding of what Wendy could do once the domain transfer was completed. Wendy is finalizing the instructions for editing and plans to share them with Darren before granting Jared access. Darren suggested that if the DNS transfer issue couldn't be resolved by the end of the next day, they could either roll it back or continue to work on it when they return on the second. The team also discussed the potential for a broken link or a 404 error if the site was accessed via HTTPS. Jon suggested that not being able to access the website for a few days was not a significant issue.

Addressing Problem and Potential Consequences

Jon, Wendy, Darren, and Dan discussed a problem that needed to be resolved by the end of the next day. Jon suggested that the issue was not their responsibility and that the other party should either fix it or take the consequences. Wendy expressed concern about the potential consequences of rolling back the changes, suggesting that it might lead to the same problem. Darren agreed to contact Candice to discuss the issue further. The team decided to monitor the situation and take a decision later.

Addressing Site Downtime and Publication

Wendy suggested sending a note to the user list about potential site downtime due to transfer issues and DNS resolution problems. She also mentioned the need to sort out publication plans for the CDI in January, ensuring correct links and placement. Wendy asked the team to figure out technical fixes by their January meeting to facilitate this. Flavio confirmed that no major changes were expected, only ensuring things are in their final places and links are updated.

CDI Publication Delay to January

Wendy informed the team that due to EDDI and the holidays' influence, the CDI publication was delayed until January. Website issues may also be a factor. Member's clarified their availability and preferred means of contact between now and January 6.

The team wished each other well for the holidays.