TC Meeting Minutes

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

ISO document review:

90 - codebook coverage

120 SDTH when published will be part of SDTL v.2 not a separate or merge into the SDTL bullet point

136 SDTL also has a UML expression; it is the word managed that was the wrong word it should be expressed

139 PIM/PSM is a CDI approach. Does version 1 of CDI have this.
Each product can be represented in separate independent syntax representations

210-213 emphasis that sentinal values in RV

328 Codebook should have x in conceptual

Why is there a role for controlled vocabulary because it is content rather than model

If you include it there are controlled vocabularies under every column as there are locations for content under each area

If CV retained it should be moved to the bottom because it is the odd product.

Controlled Vocabularies are published to support content consistency and they apply broadly across the documented areas.

SDTL also has a UML expression

342 The Controlled Vocabularies, SDTL, and SDTH are not model based in the same way. The consideration does not apply.

Dan G. was able to attend the last 15 minutes. He will take these comments and incorporate.
If there are questions as he reviews all comments, Dan G. will get back to us on Apr 24 meeting.

ACTION: Wendy will put these comments into a comment sheet and send to Dan G. and TC members later today.

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

UX review of DDI site has started

EDDI Website
Move to gitHub pages
Requested to use the DDI Repository. This was approved but it was noted that they would need to do a CName to the gitHub pages. This should not be a problem if gitHub allows one per repository - if not check back

Quick recap

The group discussed adding a missing values reference property to the represented variable in DDI 4.0, and the need for a replacement for the documentation in Confluence. They also explored the possibility of using Google Drive for organizing working group folders and note-taking, and the need for a new tool specifically for codebook generation. Lastly, they discussed the challenges of creating a new version of DDI Codebook that is compatible with COGS, and the potential of migrating users from Codebook to a version of Lifecycle not requiring identifiers.

Next steps

• Dan to update the ticket with the discussion about adding a missing values reference on the represented variable and submit a PR for this change.

• Dan to update documentation on Variable regarding the missing values reference type for version 4.0.

• Oliver to update the Google Drive concept document based on feedback received.

• Technical Committee members to review and comment on the Google Drive concept document.

• Wendy to present the Google Drive concept to the Scientific Board at the next meeting.

• Wendy to communicate the Google Drive concept to group chairs before presenting to the Executive Board.

• Darren to provide cost estimates for the Google Drive implementation.

• Technical Committee members to review and comment on Oliver's document about using COGS for codebook.

• Dan to outline the aspects of codebook that are not supported by COGS.

• Technical Committee to have a future discussion on the sustainability of codebook as a product and potential migration options.

Summary

DDI-L v4.0 issue 38

r:ManagedMissingValuesRepresentation at RepresentedVariable level · Issue #38 · ddialliance/ddimodel
Action: Add ManagedMissingValueRepresentationReference 0..1 and correct documentation in that and in Var regarding this reference

Adding Missing Values Reference Property

The group discusses adding a missing values reference property to the represented variable in DDI 4.0. Dan explains that currently, managed missing value representations can only be used through value representation references. Wendy and Flavio raise questions about combining multiple code lists and representation types. The group agrees to add the new missing values reference property to represented variables in DDI 4.0, as it's backward compatible and addresses an urgent need. Dan will update the ticket, create a pull request, and fix some documentation issues related to missing value representations.

Google Drive Concept (document in TC-drafts folder)

https://docs.google.com/document/d/1YcU2TLzIldPIKrjWq4m8YuaVX7ISHJ_8q9xVBluMYqw/edit?usp=sharing

Organizing Working Group Folders

Oliver presents a Google Drive concept for organizing working group folders. He proposes having one folder for each group, potentially grouped by product or content categories. Wendy emphasizes the need for flexibility, as some groups already have their own structures. They agree that while groups can organize themselves internally, all deliverable work should end up in the designated folders. Oliver suggests using naming conventions like "cg" for content groups and "pg" for product groups to improve accessibility.

Confluence Access and Note-Taking Solutions

Oliver and Wendy discussed the need for a replacement for the documentation in Confluence, with a focus on access issues. They considered the possibility of using Google Drive for note-taking and then copying the notes into Confluence. Wendy raised concerns about space issues and suggested that public notes should be kept in Confluence. They also discussed the idea of archiving documents and creating a template for working rules. Oliver proposed setting up a system where each group member has access to their group folder and every member has read access to all group folders.

New Group Work Structure Proposal

In the meeting, Oliver proposed a new structure for the DDI group's work, suggesting that all work should be transparent and accessible to everyone. Wendy agreed, emphasizing the importance of having a public space for all work. They also discussed the need for private spaces for certain groups, but these should be handled with sub-folders having greater access limitations, primarily to the public. The document recommends that all working group members have read access to the documents and that TC have write access. The purpose of write access is NOT to edit, but to provide comments for the working groups consideration. Wendy suggested that the new structure should be presented to the scientific board for informational purposes and then to the executive board as this is a cost item. The costs of implementing this structure should be determined and added to the document before presenting.

Google Drive Space Usage Concerns

Oliver suggested adding a list of rules for what should and shouldn't be included in the new structure, such as avoiding photo and video storage due to space considerations. Flavio raised concerns about the space usage of folders in Google Drive, suggesting a way to monitor this. Jon confirmed that large files can be identified, but it's unclear if folder-by-folder monitoring is possible. Wendy checked the total usage, but it remained unclear if individual folder usage could be tracked. The team agreed to check with Darren about cost estimates. The next Executive Board Meeting was discussed, but its status remained uncertain. The team decided to prioritize the budgeting process for the following year, with the aim of moving the current project as quickly as possible.

Using COGS for Codebook (document in TC-drafts folder)

https://docs.google.com/document/d/11ouqscCKkW1SfbNLNsZgiQtx77dZqj_b6LoYorEjLpw/edit?usp=sharing

Codebook Automation Tool Development Discussion

The team discussed the feasibility of using COGS for automating the production of codebook. Dan suggested that COGS might not be the right tool for this task, as it has limitations in handling certain aspects of codebook. He proposed creating a new tool specifically for codebook generation. The team agreed to review the document and add comments. They also discussed the need for a tool that can generate codebook without manual intervention, and the potential for external funding or development by a member. The team decided to focus on the objectives and the effort required to develop such a tool, rather than obsessing over COGS.

Codebook's Future and Compatibility Challenges

The group discusses the challenges of creating a new version of DDI Codebook that is compatible with COGS (a model-driven development approach). Dan argues that it would be more work to use COGS for Codebook than to create a separate script to generate Codebook from a non-XML source. Wendy emphasizes that users appreciate Codebook's low technical overhead and nested structure. The conversation then shifts to whether a new version of Codebook is necessary at all, with Jon suggesting that migrating users from Codebook to a non-versionable version of Lifecycle might be a better option. The group agrees that a broader discussion about the future of Codebook and its relationship to other DDI products is needed.

NEXT MEETING:
TC presentation
Codebook and Lifestyle Working Group drafts

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

ISO document
https://docs.google.com/document/d/1gWJgiEBtnb3FBFjSeBRkdqBZ4kibvY2k/edit
Send out note to TC reviewers to cc Wendy on issues sent to Dan so we can see if there are any areas requiring group discussion on April 17

Website -
The UX designer would like to conduct 10 or so UX reviews of the DDI website, especially targeting Data Managers and Developers. Do you have people you can recommend for interviews? Ideally, we'd find a mix of novice, intermediate, and expert users.

Anya Perry
Sabastian Netscher
Diana Magnuson

Ask Jared to send out an email on user list to ask for interested people

NEXT MEETING:
TC presentation - outline for 3 April
Google space draft
Codebook and Lifestyle Working Group drafts

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

OVERVIEW:

Discussion centered on specific activities for the TC regarding ISO document review, new working group proposals, and organization of a DDI google space. These have deadlines in the next 6 weeks. Specific deadlines were noted and procedures for work over the next month clarified.

TO DO:

• bring up to Dan G. the approach to get the current review by TC and CDI started

• Working Groups - Get draft ready for 27th, locate content requirements

• Google space - Oliver will draft in time to discuss before SB meeting in May

• Outstanding from previous weeks:

  • Darren to review the accessibility report and fix issues.
    in process
    Wendy and Darren to discuss website organization with Jared in their upcoming meeting.
    meeting rescheduled
    Technical Committee to draft a proposal for a unified DDI Google Docs area.
    in process
    Wendy and Oliver to draft basic mandates for Codebook and Lifecycle working groups.
    in process
    Wendy to review Jira issues list for potential Lifecycle 4.1 tasks.
    to do
    Wendy to draft an outline of the current Codebook production process.
    in process (assigned to Oliver)

SUMMARIES

ISO document

https://docs.google.com/document/d/1gWJgiEBtnb3FBFjSeBRkdqBZ4kibvY2k/edit

DONE: Contact Dan Gillman regarding type of review (product or technical document) concerns about where information on context and relationship to product suite should take place as well as plans for on-going oversight for any future required adjustments

Comments regarding type of review and process:

• I think the TC should review and give comments from the group after discussion

• The different products that are mentioned should review - TC currently does Codebook and Lifecycle and CDI should have an opportunity to review

• This is probably just a first draft that is being presented

• It seems that the review and comments are needed fairly quickly

AGREEMENT: Unless Dan G. feels otherwise, this seems to fall under the process for review of official Technical Documents (TC oversight of technical and comprehension review, but no vote). This seems to be reasonable given the additional ISO review structure. Review by TC and CDI should begin as soon as possible given Dan G.'s timeline.

Website

• Issues related to TC controlled areas can basically be changed and then reviewed by TC. Alterations can then be made.

• Content and product working groups have been asked specifically to look at Getting Started area and to think about content but also organization of information on each topic. There should be some level of consistency regarding general headings of content coverage. Flexibility to support specific needs of topic areas should be retained.

Informational:

John Kunz interested in persistent identifiers and resolution systems. He has talked some to Darren and I offered to keep him informed as we start to work more in this area. I also invited him to join the call any time it is an agenda item. This is a topical area that is on our short term work list.

TC report to SB meeting - we will be reporting, publish draft by next meeting and review

NEXT MEETING:

• ISO review off-line

• TC presentation - outline for the 27th

• Google space draft

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

AGENDA
Mop up work:

• Any March to-do items - status

• Proposals for product working groups (draft text)

• Roadmap coming items

Quick recap

The team reviewed progress on various tasks, discussed upcoming priorities, and addressed issues related to documentation and project management. They focused on specific technical challenges, including problems with Eclipse and the documentation process for their production pipeline. The conversation ended with discussions about upcoming presentations and collaborations, as well as plans for future meetings and document reviews.

Next steps

• Darren to review the accessibility report and fix the issues.

• Wendy to draft a proposal for the unified DDI Google Docs area.

• Wendy to update the colored portion of the roadmaps and ensure they are in sync.

• Darren to check in with Deirdre on Monday about the progress of the production pipeline development.

• Oliver to follow up with Ahem regarding the production pipeline development issues.

• Dan and Jon to document the process for running the FlexDoc XSD documentation generation tool.

• Wendy to send George the response about citing the Git repository and documentation links.

• All team members to review and comment on the draft texts for product groups.

• All team members to periodically review and provide feedback on the codebook documentation.

Summary

Team Progress and Upcoming Priorities

Wendy reviews the team's progress on various tasks and outlines upcoming priorities. She notes that Darren still needs to review the accessibility report, and a draft proposal for the unified DDI Google Docs area is pending. Wendy has started drafting mandates for the codebook and lifecycle working groups, with a focus on getting the codebook group started due to potential funding opportunities. She has moved several issues from the Technical Committee tracker to the website issue tracker and emphasizes the need to organize the "Getting Started" section of the website. Wendy also discusses the creation of product groups and asks for feedback on her draft document outlining their purposes and short-term tasks. She mentions the need to update and synchronize the roadmaps, noting that several items have been completed while others are ongoing. Note that post-meeting the 2 existing Google sheet Roadmaps have been synchronized and updated. There is now only a single copy https://docs.google.com/spreadsheets/d/1b390D4CpPXqtqi7-e5GhrvWdHbNEG697/edit?usp=sharing&ouid=102757977752490519555&rtpof=true&sd=true

Eclipse Issue Follow-Up and Assistance

Wendy asked Darren and Oliver to follow up on an issue with Eclipse, an integrated development environment, which is expected to be completed by the end of March. Wendy expressed concern about potential delays and suggested that the team could provide assistance or expertise if needed. Oliver mentioned that the problem might involve Java processing and building, and Wendy proposed that the team should engage them sooner rather than later to track the progress.

Production Pipeline Field Level Documentation

The team discusses the documentation process for their production pipeline, focusing on the use of FlexDoc XSD software (FlexDoc/XML XSDDoc was developed by Filigris Works). Dan suggests creating scripts to simplify the running process for each product. Wendy emphasizes the importance of documenting all processes clearly to ensure continuity.

SDTH citation question

Dan provides various links for documentation and repository folders, leaving the choice of citation to George.

MISCILANEOUS

Wendy mentions her involvement in a new group working on mapping between DDI and SDMX. She concludes by requesting team members to review draft texts and the codebook document she's been working on.

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

AGENDA

Codebook

Codebook 2.6 document folder in Google:
Codebook_2-6_Tree_draft.txt

Codebook:
High level document
Change log update
New post 2.6 Codebook working group
Funding options/needs for codebook automation
Ask Oliver to draft - current production pipeline / goals for automation
Website:
Open DAWS issues

https://ddi-alliance.atlassian.net/issues/?filter=11234

Resources content: options, outstanding questions

Quick recap

Wendy shared the Codebook v2.6 documents including the tree structure and high-level document, needed for publication. Wendy and Darren discussed the need for a more unified approach to their Google-based resources and the potential for setting up a Google account to centralize these resources. Lastly, they discussed the organization of their technical infrastructure, specifically focusing on the http://docs.ddialliance.org platform and web, and the need for a more structured approach to managing types of documents.

Next steps

• Wendy to continue filling in documentation for Codebook.

• Jon to set up the Github site for Codebook high-level documentation.

• Darren to review the accessibility report and fix issues.

• Wendy and Darren to discuss website organization with Jared in their upcoming meeting.

• Technical Committee to draft a proposal for a unified DDI Google Docs area.

• Wendy and Oliver to draft basic mandates for Codebook and Lifecycle working groups.

• Dan to merge the pull request for Lifecycle code value changes.

• Dan and team to implement Lifecycle 4.0 beta for testing this summer.

• Wendy to review Jira issues list for potential Lifecycle 4.1 tasks.

• Wendy to draft an outline of the current Codebook production process.

Summary

Codebook Review Discussion

Wendy discussed the need for a tree structure either on a high-level dock or as an additional document. She mentioned the need for reviewing what has been written to date and adding topics to the list. She mentioned the need for a document on the current development and production pipelines and asked for help in reviewing the codebook document. Darren sought clarification on whether the document would go into read the docs or cogs, to which Wendy confirmed it would be part of the production package for read the docs. Lastly, Wendy noted that Jared and Jon were looking into the cost and feasibility of updating the software for automation.

Assigning Tasks and Website Automation

Wendy and Darren will meet with Jared to discuss website automation and accessibility issues. Wendy is moving google doc requests into Jira for tracking issues. Darren agreed to review the accessibility report and fix some of the noted problems.

Organizing Website Content for Better Usability

Wendy and Darren discussed the need to organize the content of their website, particularly the "Getting Started" and "Resources" sections, to improve usability and make it easier for users to find relevant information. They agree that the website should be more user-centered and that the advisory group should get organized so that there is some guidance on User Experience (UX) improvements to the sitemap and navigation. They also discussed the need for a better information model to align the tools and products sections. Wendy mentioned that they have an issue filed on the topic and expressed concerns about what they have decision control over in making these changes. They plan to seek feedback from specific groups, including the training group, and to clarify the design authority for these changes with Jared on Tuesday.

Website Organization and Resource Management

The team discussed the need for a more unified and organized approach to their website and Google-based resources. They highlighted the presence of duplicate and outdated content, as well as the need for a more streamlined contact system. The idea of leveraging tools like Hubspot was brought up, but concerns about simplicity and professionalism were raised. Use of common tools should be balanced between simplicity of management and effective user access to content. The team also discussed the issue of multiple, disparate Google forms and documents across different groups and the need for a centralized area for these resources. The possibility of setting up a Google account to centralize and manage these resources was proposed. Wendy suggested drafting a proposal for this and getting it approved by the scientific board.

Improving Technical Infrastructure Organization

Wendy, Darren, and Dan discussed the organization of their technical infrastructure, specifically focusing on the http://docs.ddialliance.org platform. They agreed to pursue a more structured approach to information architecture, aiming to reduce the number of bookmarks and improve content organization. They also discussed the progress of the code value changes and the potential for a lifecycle group. Dan mentioned the need for implementation checks for the betas and the possibility of starting the lifecycle group before the release of version 4.0. Wendy agreed to draft up basic mandates for the code group and the lifecycle group. The team also discussed the ongoing work with the mapping project.

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

AGENDA

Update from Scientific Board meeting

Scientific Board agreed with the suggestion from TC that there should be a cross-product group on qualitative content. Darren (who is on the CDI subgroup) will draft content for the creation of a formal working group.

http://docs.ddialliance.org discussion

• Darren and Jon were unavailable today

• Confirmed the basic uses of doc.ddialliance.org which should contain:

  • generated content from production pipelines of published content including:

  • schema and specification content

  • documentation about the standard (not all pipelines generate the same mix of documents but those that are generated in other ways should also be located here.)

• Note that AWS provides us with accessible cloud storage

• Resolution systems: Controlled Vocabulary (current link is https://d2jdhhz9hcqxia.cloudfront.net/) and RDF content resolution systems (http://rdf-vocabulary.ddialliance.org )

• PDFs etc. accessible through web pages are managed within HubSpot system

MISCELLANEOUS

• What happens with contact form information (issue was filed that there is no confirmation)

  • there seems to be no autogenerated response but a statement that DDI staff will contact you

  • Jon's is the email address that contact info is sent to

• DDI-L v4.0

  • add the content to codeValue type to reflect full field of objects added to Codebook (Dan will create pull request)

• DDI-C v2.6

  • Dan has been working on the validation tool to generate and retain neat and consistent indenture. This will be switched on and content validated just before publication.

• DDI-Codebook and DDI-Lifecycle working groups should be established at point of publication. Be ready with the working group proposals by then.

• Oliver added information on the use of the Blog feature for News items to the Web Editing page

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

AGENDA:

• Website updates

• Roadmap status

• Qualitative content group

• Profiles

Quick recap

The team discussed updates and plans for the website, including the formation of a web management group and the incorporation of qualitative data representations into DDI Lifecycle. They also explored the potential of using a new format for profiles, which would allow for more machine processable and future-proof data, and the transition from the current DDI-based profiles to DCTAP. The next steps for the team were outlined, including sending information on the interoperability working group, packaging examples for TC-drafts, and ensuring the project stays on the agenda.

Next steps

• Darren to add qualitative data representation discussion to the Scientific Board agenda for Tuesday.

• Wendy to review and attempt to express existing XPath-based profiles using the new Dublin Core Tabular Application Profile approach.

• Dan to package up examples of the Dublin Core Tabular Application Profile and put them in the TC-drafts folder.

• Darren to present the Dublin Core Tabular Application Profile approach to the Interoperability Working Group.

• Wendy to ensure profiles discussion is added to a future TC meeting agenda.

• Darren to make a list of documents and their current locations for future disposition discussion (http://docs.ddialliance.org ).

• Oliver to write up directions for creating news items on the website.

• Oliver to document what features (like blogs) are being used on the website and for what purposes in the Atlassian documentation.

Summary

Website Updates

Wendy discussed several updates and plans for the website and the scientific board. She mentioned that the website update will be announced in the newsletter and that the review request has been discussed with Jared, who expressed concerns about the lack of response. Wendy also suggested moving the 'getting started' items to a top level and proposed moving resources into the 'getting started' section. She also mentioned that the web management group will be formed, with Jared's advisory group being considered.

Roadmap

https://docs.google.com/spreadsheets/d/1qIAw6zK6KIDBNSUQTFJfIjqRdkyMkj9oFTyQnNdttpI/edit?usp=sharing (see "WG Plan - items" sheet)
Wendy then shared a roadmap from the scientific board, outlining the plan for the next few years, including completing the shift to Github, revising the website, and starting overall modeling work. No major issues or problems were raised by the team. We are on plan and will address Short-Medium Term items over the spring and focus on Medium term items following that. Lifecycle and Codebook working groups will also be proposed this year.

Qualitative Data Representation in DDI

Darren discusses the potential incorporation of qualitative data representations into DDI Lifecycle. He mentions that Shauna suggested 15-20 attributes for a possible qualitative module or package. The group has been considering this idea for several years, but previous attempts were hindered by other changes and lack of activity. Flavio inquires if this would include discussions on describing images, as previously discussed in DASH. Darren confirms that it would involve referencing file packages and qualitative collections.

• Qualitative Data Subgroup

• Super narrow adding annotations in DDI-CDI.

• This needs to be a broader group

• Recommend to SB to make this a content working group (cross-product)

In the meeting, Darren and Flavio discussed the need for a more comprehensive approach to content management, rather than focusing solely on annotations. They agreed that a cross-product working group could be beneficial for integrating common design elements across different products. Wendy suggested that this should be a content working group under the scientific board, to ensure consistency and coordination across products. They also discussed the need for a common design for common things, such as classification models. The team agreed to bring this topic to the scientific board agenda for further discussion. Additionally, Wendy raised concerns about the management of broken links and outdated information on the website, suggesting a need for a more efficient system for updating and maintaining content.

Alternative Profiling Methods Discussion

Dan presented a status report on alternative profiling methods for the X path based profiles available in lifecycle. He discussed the use of Dublin Core tabular application profiles, specifically the Cesda profiles for the Question Bank, and how they could be applied to work with the Ddi models. Dan also mentioned that these profiles could be converted into checks for creating shapes for RDF serializations. He sought feedback and asked if there were any other requirements they should consider as they continue to investigate different ways to make these profiles. Darren expressed his appreciation for the work done so far.

Darren and Dan discussed the complexities of tying different elements together in XML, specifically the issue of Xpath. They agreed that the current system was confusing and that Matthew Morris had to write hacky code to overcome the Xpath problem. Dan explained that the grid they were discussing was a way to reference different elements, such as a study unit, and how it could be linked directly to a data collection. Wendy added that the data collection could live anywhere, but it needed that connection. They also discussed the future of version 4 of lifecycle, which will have XML, JSON, or RDF representation to convey content.

The team discussed the potential of using a new format for profiles, which would allow for more machine processable and future-proof data. They considered the possibility of using relative paths and value constraints, which would provide more control over the data. The team also discussed the need for a more robust tool, like the metadata validator, to handle the new format. They agreed to explore this format further and possibly publish it as an example. The team also discussed the need for clear documentation and the potential for the new format to be adopted by other groups.

The team discussed the transition from the current DDI-based profiles to DCAT, which they found to be a better solution. Dan suggested that parsing CSVs is easier and could be automated. Wendy agreed, noting that the new approach is clearer and more machine processable. Darren mentioned that he would take the discussion to the Interoperability working group and that Alan was sympathetic to the transition. Dan offered to package up the new approach as an example and put it on the shared drive for others to review. The team also discussed the potential for using the new approach for RDF shapes and the need to decouple from XML for future profiles.

• https://www.dublincore.org/specifications/dctap/primer/

• It was much clearer as documentation than the xpath profiles

• Issues of relationships from package/resource/fragment to fragment only in DDI-L v4.0 that is a problem with xpath based approach

Next Steps and Document Management

Wendy outlined the next steps for the team, including Darren sending information on the interoperability working group, Dan packaging examples for TC drafts, and Wendy ensuring the project stays on the agenda. Wendy also discussed the need for a clear understanding of document locations and rules for future disposition. Oliver confirmed that Jared now has editing rights and will be creating news items. Wendy emphasized the importance of documenting processes and features for future reference. The team agreed to meet again next week to discuss the http://docs.ddialliance.org discussion and document locations.

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

Content and organization of http://docs.ddialliance.org
https://github.com/ddialliance/docs.ddialliance.org

• Field level documentation is currently on docs

• To what extent do we want to put schema (XML, JSON, ...) on docs. CDI is currently on HubSpot file location -- should this be redirected

• In principle we should be holding things like specifications on spaces that we control AWS or http://docs.ddialliance.org rather than HubSpot

  • This makes sense - any maintainable technical artifact held on

  • Currently this would involve migrating a few dozen documents

DDI-CDI publication status

Last few changes requested by CDI are being implemented by mid-day Friday

Web review announcement approved
https://docs.google.com/document/d/1ByEfdJDmSC1rSCdjJ7gNWBzar9DNShTiQ6q0-a2L-oc/edit?usp=sharing

ACTION ITEMS:

• Oliver will put up instructions for adding to the News items on the web

• Wendy will notify Jared regarding DDI-CDI status and announcement

• Wendy will notify Jared about Web Review notice

• Darren will make a list of what documents are where (docs.ddialliance.org and HubSpot, etc.) so we can make lists and rules for future disposition

AGENDA for February 13

• 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

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

• Tested out using the Dublin core applications files that went pretty well - multiple serializations based on the content of the model level so it could be applied to all the serializations

• Functionalities:
  If this is there that has to be there - is there a possibility of tooling that can check that at a higher level
  Specifies at a structural level -
  Provide a best practice for Tool defining tools
  Schematron - XML
  ShEx and SHACL - RDF

• Members should think about use cases and functionality for profiles, as well as overall approach (profiles based on model so that it can be applied across specifications, they best practices for creating profiles for specific specifications using available tools)

AGENDA for February 20
http://docs.ddialliance.org discussion

AGENDA for February 27
Codebook (high level documentation)

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:
https://www.whatsmydns.net/#CNAME/www.ddialliance.org

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.

ATTENDEES: Wendy, Oliver, Dan, Jeremy, Christophe
REGRETS: Jon

Website shift scheduled for 18 December

• Darren is continuing work on this and coordinating with ICPSR via Jared on 18 December shift

  • General clean-up of page formating

  • Database generated pages

  • Links between pages and to documents

  • DNS changes and mappings to retain previous links for users to major pages

• Training group will review their current content pages (as changes were not made in transfer) as basis for later input for improved section

• Wendy is completing Editing Instruction Manual for consistency and will complete first major draft by the 18th for Jared's use

DDI Codebook 2.6 preparation for review/vote

• Completed:

  • Field level documentation reformatted (PR38)

  • Update on dates and version information in schema and readme files (PR39)

• TO DO:

  • update member list

  • update change log

  • complete first full draft of high-level document

  • complete production process document and plan for moving to automated production process

  • update Field Level Documentation HTML pages

    • Having a bit of trouble getting the field level doc software running on windows 11, there will be a solution just not worked it out yet

DDI Lifecycle 4.0 planning for summer release

• Making some updates to the COGS tooling from Hackathon

  • JSON tooling

  • RDF content

• Update those tooling and get out a BETA3 review in January/February

• Also, now some samples of Lifecycle 4.0 from Hackathon (RDF, JSON, XML)

  • This will allow a new set of reviewers (content to get involved

• We have more on the NECTAR publisher which supports the JSON representation, full Lifecycle, CDI, questionnaire and study level information so people can create their own examples

• Work on a secondary examples section - move all the examples to this area and improve access from HubSpot

• Creating a standardized data set and then creating examples in each of the DDI products and have content expressed across the different products

• This also supports transformation and transport between different products

• https://ddi-developers.github.io/docs/

Activities from EDDI - interest in new working groups, organizing non-product specific Roadmap activities

• Types of Working Groups

  • Technical Group - manages publication

  • Product Groups

  • Content Groups

  • Practitioners Group - Best Practices as an output

• ADD in Christophe's email

• Variable Cascade - could be an example of this type of group as they already have content

• Start as a sub-group of TC

• Christophe will follow-up on this and keep the TC informed - he will contact others interested in this

EMAIL CHAIN

RE: Practicioner's Group
Jared to Christophe:

This is to follow up on our discussion about the Marketing Working Group and the potential new Practitioners Working Group you are interested in. I'm copying Jon so he's aware on the marketing side.

I've let Jon know you've kindly offered to provide use cases from Insee, as well as that you'd be open to participating in the working group. Jon: would you be able to add Christophe to future meeting invitations?

Christophe: Can you say more about the goals of the Practitioners Working Group, including expected outcomes and participants? Once we have a written proposal, we can figure out if this should go to the Executive Board or the Scientific Board. Either can review and approve a working group, depending on the group's scope.

Refining idea to application/use cases
Christophe to Jared:

My comment was in reaction to the ddi alliance's poster inviting proposals for new working groups and I think it's a very good message. Generally speaking, I think that between the DDI training group and the technical working groups, there is room for working groups on application cases. The working group on questionnaires is a very good example of a working group. We could imagine (by making a list to Santa Claus) a working group on setting up the variable cascade, a working group on managing variables over time, a working group on the methodology for associating a concept with a variable.

I don't know if we should set up a general working group for practitioners, as the content is likely to be heterogeneous and difficult to manage, and it might be more appropriate to set up working groups on practical and fairly well-defined use cases.

I'm thinking of making a list of the work that we're planning and if the marketing group can help us to get an overview of what would be interesting and possible to address collectively and relevant, that would be great.

Links with Marketing
Jared to Christophe:

I like your idea to establish WGs based on well-defined use cases. Sounds good to start with a list of work you're planning and working with the Marketing WG. Jon's on here so he can help coordinate with the Marketing WG once that list is ready.

Establishing sub-committee, broadening to TC interests
Jon to Jared, Christophe, Wendy, Oliver:

Thanks for this Christophe, I think the DDI representation group started by INSEE/CLOSER and Constances is a good example I think of what you are thinking of, I think Frank had the idea that it would find a more official home under the Alliance at some point? But perhaps a little less? I think as they would be cross product (or at least address the different issues, they would be suited to being Technical Committee sub-groups, which would be possibly short lived to develop application use cases, I think the questionnaire group is a bit wider as it does cover a wider remit so a formal working group probably might make more sense?

Would that work? Under the current way the Alliance sets up WG’s it’s a bit inflexible and has to have more ‘paperwork’. Would that address the use-cases you are thinking of?

Discussion regarding TC
Wendy to Jon, Jared, Christophe, Oliver

Can we kick around some thoughts on this during the TC meeting on Thursday? Right now we basically have product, content, and externally focused working groups (Marketing - EB, and Training - SB). I'd like to get a clearer picture and see where cross working group coordination would be needed in terms of on-going product development as well as furthering the TC/SB goals of use case development, best practices guides or other possible outputs from such groups.

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

Quick recap

The team discussed the progress of their website project, with plans to proceed despite some issues and to launch by the end of the year. They also addressed issues related to a public URL and image functionality, and the interest of others in reviewing the DB generated content. Lastly, they discussed the use of existing tags for risk assessment purposes and the potential use of DDI metadata for these purposes.

Next steps

• Jon to write guidelines for reviewing the new website, focusing on navigation and overall structure.

• Dan to document ideas and recommendations for moving away from XML-specific profile validation tools towards more flexible, serialization-agnostic approaches.

• Wendy to attend a meeting in early 2025 to discuss DDI profile validation tools and potential expansion of the technical committee's work in this area. She will keep TC members informed.

Summary

Website Progress and Launch Plans

Wendy, Jon, Oliver, and Dan discussed the status of the website work. Wendy expressed uncertainty about the progress of database-driven pages, while Jon suggested they should move forward despite some issues. Jon proposed getting feedback from a limited number of people, possibly including someone from CLOSER, to identify any major navigation issues. Dan mentioned that they couldn't review the website at the moment due to lack of logins. Jon agreed to update the document outlining what they're asking people to review. The team decided to proceed with the website launch by the end of the year, with plans for further improvements in the following year.

Darren emailed during meeting that he would be working on this next week.

Wendy, Dan, Jon, and Oliver discussed issues related to a public URL and image functionality. Wendy confirmed the existence of a public URL and provided the link in the chat for Dan to access. Dan noticed that the images were not working, specifically mentioning the logo. Wendy agreed to add the URL to a document for future reference. Dan also suggested not sharing the URL in the meeting minutes for privacy reasons.

Discussing DDI Profile Validation Tool

Wendy discussed an upcoming meeting in early 2025 to discuss a DDI profile validation tool provided by CESSDA. As agreed in the past year, the DDI profile should not be part of the lifecycle standard and that it might be more beneficial to use existing tools for validation. They also discussed the need for better guidance on creating more flexible profiles in different serializations. Dan agreed to put his ideas into a more structured format to focus the discussion on what it would look like when the DDI profile is taken out of the lifecycle and put into this new format as well as role of TC in providing guidence for profiles in general and the use of standard tools for validation.

Using Tags for Risk Assessment

Wendy discussed her interaction with Jordan, a data librarian from USAID, who was seeking ways to use existing tags to identify combined identifiers for risk assessment purposes. Wendy suggested using the Data Relationship and Logical Record Descriptors to identify unique and complex identifiers. She also asked if anyone was using DDI metadata for similar purposes, to which Oliver responded that someone was doing something similar. Wendy will share the email chain so others can see if they can add to discussion or provide a contact.

Quick recap

Wendy and Jon discussed the progress of a project, including the addition of links to download packages and the need for a controlled vocabulary for topical content. They also considered the structure and management of their news section, deciding to archive old news items and focus on current issues. Lastly, they discussed the organization and management of various web pages, identifying redundant or superseded pages and planning to rename them to standardize the approach. Additionally, reviewed Codebook 2.6 PR 38 and approved for merging.

Next steps

• Darren to finish working on the auto-generated pages over the weekend.

• Wendy to rename the test products page and create a standard products page with appropriate hierarchies.

• Oliver to create yearly PDF archives for old news items and copy over the last two years of news to the new system.

• Wendy will download and validate Codebook v2.6 revision prior to merging

Summary

Webpage Progress and Controlled Vocabulary

Wendy discussed the progress of a project, mentioning that Jon had added to the executive board and Logos pages, and she had added version pages. She also mentioned the addition of links to download packages on each of the documents. Jon suggested that Darren was still working on auto-generated pages. Wendy raised a question about the examples page, which was previously a database but is now a standalone page. She suggested that the information could be retrieved from Drupal as separate pages. Oliver agreed. Wendy also mentioned the need for a controlled vocabulary for topical content and asked about the status of switching over from CVS.

News Section Management and Archiving

Oliver and Wendy discussed the structure and management of their news section. They considered two options: either creating a large PDF of their news archive from the beginning to the current point in time, or trying to import the entire thing from HTML. Wendy suggested archiving old news items by creating a PDF for set periods, such as yearly or every other year, and keeping only the current and past year's news. Oliver agreed with this approach, preferring to copy over the last two years of news items and having a yearly PDF for each as a news archive.

Focusing on Current Issues and Plans

Wendy emphasized the importance of focusing on current issues and archiving earlier news. She suggested that they should first complete their current tasks before opening up for people to view their plans. Jon, however, mentioned that he still needed to review a spreadsheet, which Wendy brought up for discussion. Jon indicated that there were a few outstanding issues on the spreadsheet, but he believed they were close to completion.

Web Page Organization and Management

Wendy and Jon discussed the organization and management of various web pages. They identified pages that were redundant, superseded, or needed to be archived, and Jon suggested that these should be dropped. Wendy mentioned that she had made a list of all the pages in Drupal, including old and ancient things, and Jon confirmed that he had gone through the list and made suggestions on how to dispose of them. They also discussed the process of renaming pages to standardize the approach. Jon mentioned that Darren was finishing off some tasks over the weekend and they could push the button next week. Wendy agreed to make sure the appropriate hierarchies were in place for the new site and to rename a specific page to align with the standard products page.

Codebook v2.6 PR 38

Dan verified that he had reviewed the changes in PR 38 and noted that they all looked good. Given the number of changes this will be a topic in the next public review in the event that any issues are found with the texting revision of descriptions.

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

Quick recap
Wendy and Oliver discussed the status of certain resources and standards, particularly focusing on a database-generated page and its connection to the hub. They also discussed the need for restructuring their website, focusing on the main lifecycle page, and how to structure the documentation for different versions of a product. Lastly, they discussed the organization and navigation of their documentation site, agreeing on the need to avoid duplicating content and to ensure that the site is user-friendly and easy to navigate.

Next steps

• Jon to implement basic navigation on the docs.ddialliance.org site and address the case sensitivity issue in URLs.

• Wendy to provide Jon with content for product/version pages on docs.ddialliance.org, extracted from existing product pages.

• Dan to consider adding release pages for DDI Codebook to the GitHub repository, similar to what was done for Lifecycle.

• Team to clarify the purpose and content strategy for docs.ddialliance.org versus the product pages on the CMS site.

• Navigation on docs.ddialliance.org (fix case sensitive issue)

• Basic text around each product/version (Wendy send to Jon for each)

• How to get some of these pages from google, are we looking into ways to find that - this is a separate problem and has to way with the way Google picks up information

• Coordinate information on the GitHub pages to make them more comprehensible, differentiating between package of published version and development points to GitHub

Summary
Clarifying Database Status and Hub

Wendy and Oliver discussed the status of certain resources and standards, particularly focusing on a database-generated page that was moved over but its current status was unclear. Wendy suggested reaching out to Darren for clarification on the database's status and its connection to the hub. They also discussed the need for filtering by product and version in the database, and the importance of having the correct paths and links. Wendy planned to send a note to Darren to inquire about the database's status and its connection to the hub.

From Darren: I still have to wire up the dynamic pages to HubDB. Will complete over the weekend

Check on Markup examples. Check with Darren on this. Oliver will see if he can get an export
DB on Tools check with Darren that this is on his list

Website Updates and Controlled Vocabulary

Wendy discusses the website pages and suggests checking links to ensure they are not redirecting back to the DDI Alliance site. Jon volunteers to check the membership and partners pages. The controlled vocabulary page now links to the new site, but there is no way to navigate back from it. Oliver explains that updating the PDF exports from the controlled vocabulary tool would require significant changes. The group plans to revisit organizing certain sections like annual meetings and executive board listings in the future.

Website Restructuring and Navigation Issues

Wendy and Jon discussed the restructuring of their website, focusing on the main lifecycle page. Jon expressed concern about duplication and suggested moving certain content to docs.ddialliance.com. He pointed out that the current site lacks navigation and is case-sensitive, which he deemed problematic. Wendy acknowledged these issues and agreed to address them. The team also discussed the need to reduce duplication and improve the website's structure.

Version Documentation and Navigation Strategies

Wendy and Jon discuss how to structure the documentation for different versions of a product. They consider whether to have separate pages for each version or consolidate common information on a main product page. Wendy suggests keeping version-specific details like development work on individual version pages, while moving general information like licenses and future work to the main product page. Jon raises concerns about the individual version pages appearing too terse and wants to add more descriptive content. They also discuss how to handle navigation between versions and linking to downloadable packages. Additionally, they touch on documenting older, handcrafted products like DDI Codebook alongside the newer lifecycle-based releases.

Improving Documentation Site Navigation

In the meeting, the team discussed the organization and navigation of their documentation site. They agreed on the need to avoid duplicating content and to ensure that the site is user-friendly and easy to navigate. They also discussed the need for clear navigation on the Docs page and the potential for improving SEO. The team decided to create a static website as a flattened version of the existing links on the CMS. They also discussed the need to link individual product pages to the main page and to improve the site's accessibility from Google. The team agreed to continue working on these issues to improve the site's usability and navigation. We need to be able to navigation from child to parent (example: version to product) on the CMS pages as well as adding something into the html on the git hub to return to the CMS site.

ATTENDEES: Wendy, Oliver, Dan, Jeremy, Darren (Jon in follow-up meeting)

REGRETS: Flavio

Quick recap

Wendy went over the suggested changes to the Product pages and will contact Jon for additional feedback. Wendy, Darren, and Dan discussed changes to the CV and the integration of older versions into the main DDI website. They also discussed the implementation of a new feature and the ongoing CDI vote, with plans to address any feedback or new tickets. Additionally, Wendy discussed status of DDI Codebook and her plans to follow through with Adrian concerning the overall structure of the field level documentation.

Next steps

• Wendy to send the changes made to the generated sections of the web site by Jared to Oliver and Darren again.

• Darren to make final changes to the postman collection for the CV section within the next week.

• Darren to explain to Sanda how the archived versions page has been integrated into the main page.

• Jon to provide additional comments on the content distribution of product pages

• Jon to contact Darren regarding a means of verifying document links prior to web site review

• Wendy to update product level pages in HubSpot

Summary

Web site preparation for Member Review in November

Wendy went over the suggested changes in the product page and version page content. This can be put in place now and determination of what content should be in http://docs.ddialliance.org and what is held in the web page. Currently the thought is that the Product page is on the web site with links to version level content held in http://docs.ddialliance.org . This was further discussed between Wendy and Jon at a follow-up meeting (Jon was unable to attend the initial meeting due a failure to move the meeting time to adjust for Europe implementing DLT this past weekend. Note that Europe and North America will be aligned by next week. Jon will send out comment on the division of content. Jon is also going over the remaining pages in Drupal and how they should be handled.

CV Changes and Integration Updates

Wendy and Darren discussed the changes made by Sanda and the status of the CV. Darren mentioned that Sanda was not fully satisfied with the changes, but he was working on the postman collection and expected it to be ready in the next week. Wendy suggested that the final changes on the CV section could be made while people started reviewing it. They also discussed the integration of older versions of CVs (archived versions) into the main DDI website, with Darren explaining that the original page was now incorporated into the new one. Wendy agreed to send Darren the link to the archived versions page for further clarification.

DDI Lifecycle v4.0 BETA2

Cardinality changes were entered in GitHub, approved and merged into the master. BETA2 is ready for review. Dan will draft announcement with plan to release for review next Monday.

Codebook

Wendy and Dan discussed work by Adrian Dusa on the Codebook field level documentation. Wendy has reviewed and addressed an earlier concern of Dan's regarding possible loss of content. This does not seem to be the case and Dan will relook at the documentation. Wendy had some questions regarding layout discissions and will share her comments with Dan to see of they are anything more than cosmetic. Adrian is avaiable for further consultation.

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

Quick recap

The meeting focused on addressing website and system issues, including user access complaints, project deadlines, and restructuring of product pages and documentation. The team discussed potential solutions such as cloud migration, shifting from Drupal to HubSpot, and consolidating information into more succinct formats. They also agreed on various action items, including reviewing historical files, updating internal links, and moving content between platforms to improve organization and accessibility.

Next steps

• Wendy to create and share a clear structure diagram for product pages, showing what content goes where between the main site and docs.ddialliance.org.

• Jon to review the spreadsheet of old pages Wendy will send and triage them for keeping, archiving, or removing.

• Darren to complete his assigned tasks on the content spreadsheet within the next two weeks.

• Wendy to send database content changes from Jared to both Jon and Oliver.

Summary

Addressing Group Access Complaints

Wendy discussed the increasing complaints about users' inability to access certain groups. She sought the team's opinion on whether to move the system to a cloud space, considering the potential costs and security concerns. Jon expressed skepticism about the need for a change, suggesting that the issue might be with users' ability to use the system, not the system itself. He proposed monitoring the situation rather than disrupting the current setup. Wendy agreed to close the matter for now and monitor the situation further. She will contact Jared regarding this.

Website Project Progress and Plans

Wendy, Darren, Jon, and Oliver discussed the progress and future plans for their website project. Wendy expressed concerns about the deadline for the review in November and the need to shift from Drupal to HubSpot. Darren confirmed he could complete his tasks within the next two weeks, but needed to liaise with Jared about email templates. Wendy and Darren agreed on prioritizing the database-driven pages for the review. Jon offered to update the database-driven content once the database-driven stuff was up and running. Oliver confirmed he would handle the content changes and Wendy agreed to copy Jon with the updates. The team agreed to aim for a review starting the sometime during the first week of November.

What MUST be done prior to review period?
Mail - templates - Darren will liaise with Jared
All done over the next 2 weeks
Data base driven pages
Document links in the pages (the links should just work when we move the URNs)

Generated pages
Updates since pull to database contents - send to Oliver and Jon
News section - new articles
Publications
Workshops and Webinars page - Jon
Conference pages - Wendy move as HTML (verified 2024-10-26 that this was completed in August)
Dagstuhl - Wendy move as HTML (verified 2024-10-26 that this was completed in August)

Website Management and Document Review

Wendy, Jon, and Darren discussed the management of various pages and documents on their website. They agreed to move certain pages to a standard HTML format and to review the historical files for potential archiving or removal. Wendy shared a list of pages, including older ones, and asked for a decision on their retention or disposal. Jon agreed to review the list and make recommendations. They also discussed the need for a clear criteria for handling additional pages outside of the product sections. The team decided to address these issues before the review.

Product Page Restructuring and Updates

Wendy, Jon, and Darren discussed the restructuring of their product pages. They agreed to consolidate the information into more succinct pieces, directing users to the current version and then to specific product pages for more detailed information. They also discussed the need to update internal links and the potential for some links to not work due to changes in the file structure. Darren suggested a single overview page for quick navigation to all versions, with more detailed information on product-specific pages. The team also discussed the need to move some documents and update links, with the possibility of needing to spend an afternoon checking each page.

DDI Website Product Page Issues

Jon and Darren discussed issues with the DDI website's product pages. They notice that the 3.3 version page lacks content found on the live site. Jon suggests moving that additional content from the live site to the 3.3 docs on GitHub. Wendy joins and explains there was an agreement to consolidate product information, but her audio keeps cutting out.

Product Page Restructuring and Documentation

The meeting discussed the restructuring of product pages and documentation. Jon and Wendy agreed to move most of the content of version pages to http://docs.ddialliance.org , with only essential links remaining on the current site. They also discussed the need to avoid duplicating content and updating information in multiple places. The team decided to move the publication repository from BitBucket to GitHub. Wendy committed to sending a spreadsheet detailing the changes and action items to Jon and others. The team also discussed the need for a clear structure for the new pages and the possibility of moving the CDI Repository under the DDI Alliance.

High level documents and Best Practices

Future item to review these types of documents in terms of how they can change into versioned documents where old version specific information is moved an appendix. Much of the information in these documenta apply to multiple versions. This would also improve the ability of product groups to keep these up to date.

ATTENDEES: Wendy, Jeremy, Dan

Quick recap

Wendy discussed the upcoming vote process, a future discussion on handling documents on the new website including issues of document preservation, and the potential transition of mailing lists from Google Groups to Discourse. She also reviewed a pull request with Dan, focusing on the cardinality of certain elements, and they discussed the process of resolving issues on GitHub. Lastly, they discussed the upcoming Beta release.

Next steps

• Wendy to send out a proposal for the product section layout and information structure for review by the team.

• Dan to triple-check the cardinality changes and send an email to Wendy for final review before releasing the next Beta version.

• Wendy to send out Jared's request about investigating Discourse as an alternative to Google Groups for broader team input.

Summary

Upcoming Vote Process, Document Preservation, and Improvements

Wendy discussed the upcoming vote process, which is expected to start next week and last for four weeks. She mentioned that they are waiting for a slide deck from Arofan, which needs to be licensed under CC BY. Wendy also touched on the topic of document preservation and the use of Zenodo for this purpose. She expressed her intention to ensure that they don't lose any information during the transition process. Wendy also discussed the need to improve the layout and accessibility of certain information, aiming to enhance user experience and efficiency. She committed to sending out her understanding of the proposed changes for feedback and potential modifications. Lastly, Wendy mentioned the need to move certain material by the end of the month and planned to communicate this via email or a Google document before discussing it in a meeting.

Transitioning Mailing Lists to Discourse Discussion

Wendy, Dan, and Jeremy discussed the potential transition of mailing lists from Google Groups to Discourse due to limitations and recent issues. Dan suggested the Alliance consider a hosted cloud plan from Discourse, costing $1,200 per year, and Jeremy agreed that Michigan IT would need to investigate if the Alliance wanted to manage it themselves. The final decision on using Discourse and its associated costs would be up to the Alliance. They also discussed the potential issues and benefits of setting up a server and managing integrations, databases, and updates. In terms of general management of lists, Wendy suggesting a future web group could discuss ensuring that we had individuals identified to handle content management. The possibility of importing previous Google group or listserv content into a new product was also discussed, with Dan suggesting starting with the business plan and then downgrading if possible.

BACKGROUND from Jared:
With the transition to the new website and related infrastructure, I'm interested in revisiting moving our mailing lists to Discourse (https://www.discourse.org/). We'd discussed a possible transition five years ago (below), but ended up using Google Groups instead.

There are limitations with Google Groups and the new infrastructure may open better options for us hosting our own Discourse server for ddi-users, ddi-srg, and the working groups. Is this something the Technical Committee could investigate?

Just one more point on this -- I'm noticing the very occasional user who isn't able to subscribe to Google Groups. Not exactly sure the reason. Seems like a recent development with Google Groups.

(below content)

The idea is to replace the ddi user's email listserve with a tool that can do both email and web based discussion.

Discourse is open source forum software what has this capability. The idea would be to create a https://community.ddialliance.org where DDI discussion could take place. There is also the possibility to import a mailman archive (current ddi-users list software) into discourse, so past discussion can be surfaced onto the web as well.

ICPSR could provide the hosting of the docker image, or the DDI Alliance could rent a vm from a cloud provider. I would be happy to help with the setup of the system.

I don't know how this fits in with your discussion about listserves. I think that announcement lists are different from discussion lists, perhaps there is some overlap as well. The idea is to replace the ddi user's email listserve with a tool that can do both email and web based discussion.

Discourse is open source forum software what has this capability. The idea would be to create a https://community.ddialliance.org where DDI discussion could take place. There is also the possibility to import a mailman archive (current ddi-users list software) into discourse, so past discussion can be surfaced onto the web as well.

ICPSR could provide the hosting of the docker image, or the DDI Alliance could rent a vm from a cloud provider. I would be happy to help with the setup of the system.

I don't know how this fits in with your discussion about listserves. I think that announcement lists are different from discussion lists, perhaps there is some overlap as well.

Document from original discussion in 2019/2020
https://docs.google.com/document/d/1X9B8unp6yOz6jGJ1rw-cCS7u5pWw7kqw-z6AHnax1kk/edit?usp=sharing

SPECIFIC POINTS from today's discussion:

https://www.discourse.org/pricing

It’s easier pay the money and have the 5 staff accounts to manage it
Can we import previous listserve/google group if we use their product?
Can you start with business plan and downgrade as we have a long set of content q&a

Review of Pull Request and Element Cardinality

Wendy and Dan discussed the review of a pull request, focusing on the cardinality of certain elements. Dan confirmed that he had reviewed all the elements and updated those that were initially marked as 0 to many. Wendy expressed confusion about the resolution of some issues she had raised in the pull request, as she didn't see any comments on how they were resolved. Dan acknowledged these issues and indicated that he had dealt with them, and clarified how resolution information was shown in GitHub.

GitHub Process and DDI Lifecycle 4.0 BETA2 Release

Dan and Wendy discussed the process of resolving issues on GitHub, with Dan providing guidance on viewing individual commits and changes. They also talked about the upcoming BETA2 release and the possibility of additional issues being added to it.

ATTENDEES: Wendy, Darren, Dan, Jeremy, Flavio

Quick recap

Darren, Wendy, and Dan discussed the readiness of the postman collection and the need for a written implementation plan. They also discussed the need to update the sequence property in their system and the progress of their project, with a focus on the potential for an RDF representation of the DDI codebook. The conversation ended with plans for a hackathon challenge.

Next steps

• Darren to email Sanda about the postman collection and HTML page revisions being ready and discuss making it available next week.

• Darren will remind Arofan to provide the implementation plan in writing for CDI-100 as requested by the Technical Committee.

• Dan to file an issue regarding the RDF code URIs and version stability.

Summary

Postman Collection Readiness and Implementation Plan

Darren and Wendy discussed the readiness of the postman collection and the need for a written implementation plan from Arofan. Darren agreed to send an email to Sanda and Jared to update the CV page and set up a webinar on this new system. Wendy will initiate the vote process with Jared once the written implementation plan is received. Dan and Darren also discussed the possibility of implementing a version-independent URI for the CVs, which Dan suggested could be a future enhancement. The team agreed to proceed with the current plan and to address the version-independent URI issue later.

Updating Sequence Property and Cardinalities

Wendy and Dan discussed the need to update the sequence property in their system. They noted that the property was already ordered in the Beta version, but other properties were not. Dan has made revisions addressing comments Wendy made on the Pull Request (#48). Dan mentioned that he had updated the cardinalities and the order, but there were some choices that didn't match their normal naming convention. Wendy agreed to go through the choices to ensure consistency. Dan will make changes and include in this pull request.

Project Progress, Documentation, and XML Linter

Dan and Wendy discussed the progress of Codebook work, with Wendy committing to complete certain tasks by the end of the day. They also discussed the need to re-engage Adrian regarding the documentation. Dan will implement the format validation using XML Linter and suggested the addition of instructions on how to use the XML Linter to reformat it before making changes. Wendy agreed to look at Adrian's previous work and compare it with the current documentation to ensure consistency. They also discussed the need to check each individual element in the documentation to ensure proper formatting and content.

DDI Codebook RDF Representation and Ontology

Dan and Wendy discussed the potential for an RDF representation of the DDI codebook, given the status of DDI Lifecycle as a superset of DDI Codebook. They considered creating a DDI codebook ontology, reusing URIs from the lifecycle model. Wendy emphasized the need for a clear production process and the progress towards automated production for their products. Dan agreed to write up a challenge for the upcoming hackathon and to forward it to Wendy for additional ideas.

CDI pre-vote webinar

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

AGENDA:
DDI-CDI submission
Timeline and steps needed to initiate Vote
Webinar Oct 3, (need to reschedule TC)
CDI-101
CDI-100
Next Steps
Getting 4.0 BETA2 out

Quick recap
Wendy discussed the upcoming webinar and the subsequent vote, as well as the implementation of an automation system by the CDI group. The team also discussed their schedules, the upcoming webinar, and the resolution of the two issues Jeremy filed in CDI Jira. Lastly, Wendy discussed the completion of the build scripts for DDI-CDI script for the DDI space, which is expected to be completed by the end of 2024, and the need for a build script that can be run in Github actions.

Next steps

• Wendy to communicate with CDI group about the need for a build script that can be run locally or in Github actions, clarifying expectations and timelines.

• Achim to develop the build script for CDI implementation, aiming for completion by the end of 2024.

• Oliver to assist with integrating the CDI build script into Github actions once it's developed.

Summary
Webinar Discussion and Automation System Update

Wendy discussed the upcoming webinar and the subsequent vote, which is expected to take place after the event and last for a month. She also mentioned that the CDI group has asked for clarification on providing a timeline for implementing their automation system. Wendy noted that Jared had sent out a notification for the webinar and that Flavio was reviewing 97 issues in the Jira issue tracker to determine which have been resolved. This should be completed prior to the webinar. There were no objections or concerns raised about the proposed timeline or steps.

Schedules, Webinar, and Lifecycle Updates

Wendy, Oliver, Jon, Dan, and Jeremy discussed their schedules and the upcoming webinar. Jon mentioned he would be away for the next three weeks, and Dan suggested cancelling the meeting next week unless there was a significant agenda item. Dan also planned to complete an ordered elements in Lifecycle task soon and intended to discuss the BETA2 of Lifecycle before Jon's return. Wendy agreed to these plans and proposed to discuss on email and only meet on this if necessary if necessary.

Project Implementation and Process Details Discussion

CDI-101 has been resolved as Jeremy suggested. Wendy will inform Arofan so they can close this issue. Regarding CDI-100 she also mentioned a request for more information on the implementation of a process, which was initially unclear. Wendy clarified that the team wanted more details on the implementation, not just the process itself. The team had previously attached a document outlining the process, but Wendy suggested they needed more information on its implementation.

Script Implementation for DDI Space Automation

Wendy discussed the implementation of a build script for the DDI space, which is expected to be completed by the end of 2024. The script, to be developed by Achim, will be used to automate the system once data is extracted from EA. Wendy clarified that the long-term goal is to have the build script run in the DDI space, not in a separate pipeline. Jeremy and Dan suggested that the script should be run either locally by developers or in a continuous integration system like Github actions. They also emphasized the need for a build script that can be run in Github actions, which can be set up after the build script is developed. Oliver suggested that the script should be runnable inside Github actions, and that the team should maintain the Github actions. Wendy agreed to clarify these points to Achim and to seek specific timelines and responsibilities for the project.

Background information on CDI-100

See Section I: Production Flows in process document (page 2)

Achim is starting work on implementation of an automated production line (jar files, etc.) following Dagstuhl (area 1 of funding request) Goal is to complete by end of 2024

Working in AW space - contact with Oliver on getting the pipelines into DDI space (eventually get these on GitHub Actions)

Read issue CDI-100 comments

What specifically do we need from CDI - prior to vote

We asked for a clarification of what needed to be done, who was working on it, what was the timeline. Do we need this from them in writing? If so do we summarize our understanding and then have them sign off on it? This could be fastest as much of it has simply been discussed.

TO DO DURING MEETING:

CDI-101 can we tell them this is acceptable. Basically, Achim agreed with TC and they retained only the canonical XML schema in the package (other will be provided as a convenience schema).

CDI-100 Review comments
What specifically do we need from them. I have notes from the CDI meeting about planned steps and asked Arofan to clarify the statement that a document is in the works from the issue comment.

Note that there is step-by-step documentation being drafted, but the overall production flows are described in the syntax representation document. This will be made final in the near term.

Is the movement to Git workflows a current imperative or a goal?

FROM AROFAN
That comment needs updating, as per our discussion today. I am happy to write up whatever is needed, but at this point it seemed like that section of the syntax representation document was good enough.

I would like to see specifics - with links to the correct versions of each piece of code - added when we have the pipeline set up. At this point, though, I am not sure that makes sense. The idea would be to have a common code repository and full documentation in reference to that repository, presumably for all of the TC products. I can work with Achim as this develops further.

Website work update:
Management document
https://docs.google.com/document/d/1TgC-KEng2cccXU_ugvvhHIjrx4SC9HU5xj0XmZ3eTcY/edit?usp=sharing Darren to email Sanda about the postman collection and HTML page revisions being ready and discuss making it available next week.

Darren will remind Arofan to provide the implementation plan in writing for CDI-100 as requested by the Technical Committee.

Dan to file an issue regarding the RDF code URIs and version stability.

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, Oliver, Darren, Dan, Flavio, Jeremy

AGENDA:

• DDI Lifecycle Codelist CV versions and distribution options via AW

• Agreement between TC and ICPSR regarding website management

• Defining admin and content positions for website

Quick recap

The team discussed improvements to DDI-Lifecycle Codelist version of CV information distribution, including versioning, file layout, and code list management. They explored website management roles, responsibilities, and the transition process for their project. The team also addressed document relocation and the need for a timeline and checklist to guide the project's progress.

Next steps

• Dan to create an example of the proposed versioning changes for DDI code lists of CVs and share it with the group.

• Wendy to write up clarification on the roles and responsibilities for website administration and content management.

• Wendy to create a Google spreadsheet with a timeline and checklist for the website migration, including dependencies and key dates.

• Dan to continue working on the ordered properties for DDI-Lifecycle 4.0 Beta 2.

• Wendy to contact John to clarify the location and organization of documents moved from the website to http://docs.ddialliance.org .

Summary

DDI Lifecycle Codelist CV versions and distribution options via AW:

Dan proposes creating a new file and disk layout for distributing DDILifecycle information and code lists, allowing for automatic listing of available versions. He suggests changing the versioning to reflect content changes in the DDI metadata version and storing the user-provided version in the DDI UserID. Darren agrees to consider these proposals for improving versioning and identification. Oliver clarifies that this would not require changes to the publication system.

• Versioning System for Translations Discussion

  • The team discussed the versioning system for translations and its implications. They agreed that a version change could occur if there are structural changes to the vocabulary, such as new categories or deleted categories. However, they also noted that a version change could occur without any content change, which could be confusing. The team also discussed the need for a programmatical way to determine if a version change is necessary for an individual concept, which would require integrating a comparison process into the creation process. They concluded that this would be a complex task, potentially requiring a new management system.
    Current CV Versioning policy
    https://ddialliance.org/controlled-vocabularies#policy

• Managing DDI Content Updates and Code Lists

  • Dan proposed a solution to manage and compare updates to the DDI Content, including a manifest file to list all available content and different versions. He suggested this to simplify the process of importing and translating DDI code lists into their tools. Darren and DDI agreed that any changes to the code lists should occur at the point of generation to ensure consistency. Oliver clarified that the current code lists are published in the DDI Alliance CV system as XML files. The team agreed to consider Dan's proposal for a more streamlined process.

• Versioning Mechanism and Transition Concerns

  • Oliver and Darren discussed the versioning mechanism between the SKOS and the code list representation. They considered the implications of having multiple versions of the same concept, such as a telephone entry, and how this would affect the transition between the two systems. Oliver expressed concerns about the uncertainty of where to land when transitioning from one version to another. The team also discussed the possibility of using an XSLT to produce the code list and category scheme, but Oliver was still unsure about the specifics of the transition process.

• Code Values and DDI Code List Discussion

  • Dan and Oliver discussed the concept of code values in the DDI CodeList, with Dan explaining that users would input these values in the CV properties. They also discussed the link between the CodeList and the SKOS ID for the code list, with Dan clarifying that the user ids in the codes are not versionable and always have the same version as their parent versionable. Oliver suggested the possibility of switching the user id into the code using an attribute pair. Dan confirmed that the code entries have the agency id, version, and user id, but they are not versionable objects and are treated differently in the DDI-Lifecycle.

• Discussing Controlled Vocabulary Terms in Data

  • Wendy and Dan discussed the use of controlled vocabulary terms in their data. Wendy expressed confusion about the purpose of these terms, particularly in relation to code lists. Dan clarified that the controlled vocabulary terms were meant to provide values for code value properties in the metadata, and should not be used as code lists for variable domains. Wendy agreed, noting that the terms could be useful for large datasets like country codes, but should not be reused. The conversation ended with Wendy expressing clarity on the purpose of the controlled vocabulary terms.

• Discussing Version Categorization Mechanism Changes

  • The team discussed the need to change the mechanism for categorizing versions, with Dan proposing a simpler system where the version increases to signify a new release. However, Darren expressed concerns about potential confusion if the changes aren't clearly explained. Oliver and DDI agreed that a detailed example of the proposed changes would be helpful for understanding the issue. They decided to create such an example and revisit the topic once it's ready.

Website Management Agreement Discussion

Wendy discussed the agreement between TC and ICPSR regarding website management. Darren suggested that the agreement could be between the TC and him, rather than ICPSR. The group agreed to proceed on this basis, with the understanding that the TC would manage the website. Darren also suggested that the website could be deployed onto the same AWS platform as http://docs.ddialliance.org next year, to keep everything on one ecosystem. The main point of clarification was ensuring that the TC's role in managing the website was clear.

• Website Management Roles and Responsibilities

  • The team discussed the roles and responsibilities of the four people managing their website. They agreed that two roles would be for content management and two for administration. The content roles would involve maintaining the website's content, currently dividing this in Product content and all else (primarily covering Admin and the Learn section). Distribution of content responsibility can shift was workloads and converage changes occur. Adminitrative roles would include branding, styling, and templates, as well as managing the database and file content. The administration roles would also include overseeing the website's performance, organization, and policy decisions. The team also discussed the possibility of an archivist role to monitor changes and ensure consistency across the site. They agreed that any major changes to the website would need to be reviewed and discussed by a broader group or the Executive Board, if there were costs involved.

• Admin roles

  • Maintain branding, organization, styling, templates

  • HubDB database management

  • File management

• Content roles

  • Product content

  • Admin/non-product content

• Archivist

  • Write up archivist

  • Analytics - could reside elsewhere

• Policy decisions - Initiated by TC with external review

Transition Timeline and Checklist Discussion

Wendy discussed the need for a timeline and checklist for the transition of their project. She agreed to create a Google spreadsheet to outline the tasks and dependencies. The goal is to have the transition completed by December 31st. Wendy also mentioned the need to handle content changes and ensure consistency between the ICPSR site and HubSpot site until final switch over is made. Darren suggested that the TC report on the Face-to-Face could be expanded into a chart with dates. Wendy also mentioned the agreement with ICPSR to shift over the entire ddi alliance.org DNS area and the status of the DDI-Lifecycle 4.0 Beta 2. Dan is still working on the ordered properties and once ready, they can send out the beta.

• Document Location Inquiry and Discussion

  • Wendy inquired about the location of documents moved by Jon into http://docs.ddialliance.org . Dan confirmed that he couldn't see any documents added to the http://docs.ddialliance.org , suggesting they might have been moved elsewhere. Darren found the top-level folder where Jon had copied all the files, which amounted to nearly a gigabyte's worth. Wendy decided to consult Jon to determine if this was their permanent location or a temporary one. Links to documents from web pages will need to be updated.
    Moved documents from website
    https://app-eu1.hubspot.com/files/144531336/?folderId=112327536857

FUTURE MEETINGS:
Wendy encouraged anyone with issues to send her a note for the next meeting.

ATTENDING: Wendy, Oliver, Jon, Darren, Dan, Jeremy, Flavio

Sep 05, 2024 09:56 AM Eastern Time (US and Canada) ID: 596 245 942
Quick recap
The team discussed the potential transfer of the ddialliance.org domain to their management, with a focus on setting up the same records in the current zone and then asking the current registrar to switch the name servers. They also discussed the coordination and management of legal and administrative tasks related to the UKDA project, with a focus on identifying roles and responsibilities for content management. Lastly, they discussed the need for a detailed report on the size of the content moved from the old site to HubSpot, the creation of a high-level document for codebook, and the progress and future plans for the DDI-Lifecycle version 4.

Next steps
Wendy to send a note to Jared about coordinating a call with Darren, Dan, and the appropriate ICPSR team members regarding the DNS transfer of http://ddialliance.org .

Wendy to follow up with Jared about the legal/management paperwork for the website and base configuration responsibilities.

Dan to submit a pull request with a first pass of marking ordered properties in DDI Lifecycle version 4 by the end of the month, in preparation for Beta 2 release.

Summary
DDI Alliance Domain Transfer Discussion

Wendy, Darren, and Dan discussed the potential of transferring the http://ddialliance.org domain to their management. They considered the pros and cons of this move, with the ICPSR team being in favor of the whole domain transfer. Darren suggested that the process should be straightforward, but they would need to set up the same records in the current zone and then ask the current registrar to switch the name servers. Dan proposed the possibility of transferring the resources to their account or setting it up to replicate it. Wendy agreed to set up a call with the right person in the DevOps or network team, including Darren and Dan, to further discuss the process.

UKDA Project Legal and Administrative Coordination

Wendy, Jon, and Darren discussed the coordination and management of legal and administrative tasks related to the UKDA project. They clarified the roles of named individuals in managing the AWS/HubSpot platform, with two individuals each for content and administration. They also discussed the need for clear roles and responsibilities, particularly for content management, and the potential for an oversight archivist role. The team agreed to identify these roles and individuals, with Darren offering to be an admin contact until the project goes live. Wendy suggested that they need to flesh out the roles and responsibilities further and identify the necessary people for the setup and ongoing management of the project.

Project Updates, Reports, and Expense Reimbursements

Wendy discussed the need to follow up with Jared regarding the legal aspects of a project and mentioned that she would be sending a note to Jared on this later in the day. She also mentioned the meeting report from the Technical Committee F2F and asked for feedback on the current draft. Jon suggested that the report from the face-to-face meeting was excellent and had no comments. Wendy also mentioned the need to fit the report into Jared's framework and asked for input on her list for the overall report. She also reminded the team about the 45-day deadline for expense reimbursement requests. The team discussed a form from Hilda that seemed to be mixing up two different things - the funding report for Jared and the annual or 6 monthly report from the working groups. It was decided that Wendy should send the report to Hilda and the financial report to Jared.

HubSpot Content Transition and Policy Discussion

Wendy expressed a need for a detailed report on the size of the content moved from the old site to HubSpot, including the number of pages and gigabytes of data. She also emphasized the importance of having a clear policy on what content should be archived and what should be retained as pages or moved to PDFs. Wendy suggested that a timeline for the transition should be established, with a goal of completing the move by EDDI with a hard deadline of December 31st. She also highlighted the need for communication with the DDI community about the changes and the expected timeline. Oliver agreed to work on a proposal for the transition of news elements from the old site to HubSpot.

Creating a High-Level DDI-Codebook Best Practices Document

Wendy discussed the need for a high-level document for codebook, which would contain best practices and information on the use of identifiers and controlled vocabularies, etc. She questioned whether this document should be part of the codebook package or a standalone best practices document. Dan suggested it should be a standalone document, as the usage document should not be tied to a specific version of codebook, given its backwards compatibility. Wendy agreed, noting that this would provide more flexibility in the document's tone and content.

DDI-Lifecycle Version 4 Progress and Future Plans

Wendy, Dan, and Flavio discussed the progress and future plans for the DDI-Lifecycle version 4.0 BETA2. Dan suggested a first pass at marking properties as ordered before setting out a BETA2 for review. Wendy agreed to this and mentioned a preliminary list from a previous issue. Dan proposed to submit a pull request with his first pass of ordered elements and asked for feedback from those interested in the RDF version. The team aimed to have the BETA2 version out by the end of the month (September). Flavio was tasked with reviewing the draft report for the scientific board meeting, which Wendy will send in by Monday. The funding report will be completed and sent to Jared. The team also discussed the roadmap for the next 12 to 18 months. This will be on next weeks agenda.

ATTENDEES: Wendy, Jon, Darren, Jeremy, Dan
REGRETS: Oliver
Relevant links:

XKOS:
https://rdf-vocabulary.ddialliance.org/xkos
CONTROLLED VOCABULARIES
https://ddialliance.org/controlled-vocabularies

redirect to:
https://rdf-vocabulary.ddialliance.org/cv

CDI example of HTML redirect
https://rdf-vocabulary.ddialliance.org/ddi-cdi/Agent

Quick recap

The team resumed collaboration with a content professional, discussed the progress of the RDF project, and considered using GitHub as a production tool. They also prioritized tasks for the upcoming quarters, identified key areas of focus, and discussed access and responsibilities for the new website. Lastly, they highlighted the need for finalizing content due to upcoming changes in best practices and the completion of the DNS change.

Next steps

• Darren to create a task list of remaining items for the website project, including data-driven pages, templates, styling, and mail shots.

• Darren to work with Michigan to redirect the RDF vocabulary URL and test the preservation of headers in the 301 redirect.

• TC members to review the roadmap document and provide feedback on priorities for the last half of 2024 and first half of 2025, including suggestions for new items or changes to existing ones.

Summary

Resumed Collaboration and Content Updates

Darren reported that they have resumed collaboration with the content professional, enabling re-editing of pages. He proposed creating an item list of outstanding tasks for the next team meeting. Darren also sought clarification on the tasks related to mail shots. Wendy emphasized the urgency of finalizing the content, highlighting the upcoming changes in best practices and the need to inform the working groups about the process. Lastly, Darren noted that the DNS change had been completed by DM , (Michigan).

RDF Project Progress and Redirect Testing

Darren discussed the progress of the RDF project, focusing on the upcoming redirect of the DDI-CDI page to the new RDF host. He also mentioned the need to test the redirect process to ensure the preservation of headers and the functionality of the redirect. Darren further shared his plan to improve the user experience by making concept URIs more accessible on the HTML pages and intended to discuss this with Oliver. The team also considered the idea of a poster session or webinar to present the project's progress and new infrastructure changes, with Jon suggesting a 15-20 minute session on the website. This could be combined with Roadmap session, and CV presentation.

GitHub Production Tool and RDF Ontology

Dan and Wendy discussed the use of GitHub as a production tool for XKOS and codebook. They recognized the need to expand the roadmap to include website-related work they recently took on. Wendy explained the Equivalency group's work on developing an RDF Ontology model to represent common content and concepts across DDI products. Wendy and Dan explored the idea of creating an underlying database mapping objects and content across different DDI products to enable consistent transformation and facilitate high-level understanding of DDI's overall coverage.

Prioritizing Tasks and Website Responsibilities

Wendy discussed the need for prioritizing tasks and identifying key areas of focus for the upcoming quarters. Wendy requested input from the team on their priorities and asked for a list of tasks that need to be broken out or given new subheadings. The team also discussed the access and responsibilities for the new website, with a limit of four people identified for administration and content. The team expects the CDI work to be completed by late September or early October.

ATTENDEES: Wendy, Jon, Oliver, Darren, Jeremy, Dan
CDI update

Roadmap/timeline requirement
There are documents on what is required and funding for implementation was part of this years request. They will prioritize this work product. Achim is back on Sept 11 and we should get roadmap and timeline shortly afterwards. Achim and Deirdre will work with Oliver on setting up pipelines in established DDI production work areas.

CDI timeline
They plan on submitting the package for voting process by Friday 20 September. Out goal will be to get it turned around by 27 September or shortly thereafter. Tentative date for the webinar is Thursday 3 October (of following week if necessary). The voting period should start within a 3-7 window on either side of this date. Wendy will coordinate with Jared. I noted that we will still be running a dual website at that point so the presentation of products may shift some pre- and post-voting period.

CV update
Request for DNS change should be made in next few days and be functional approximately 48 later. This will then be tested, followed by deployment, and then set up of RDF vocabulary resolution platform. Arofan will check on status 3 September.

Sanda wants to do more changes on the home page. Should be live next week. Entry shifts from Jared to Darren

HubSpot update
HubSpot needs to switch to US HubSpot outlet
Jon is talking to Jared on Monday to get the quote sorted and processed
We have a contact on the finance end at DDI
Darren has export .5 GIG of files and tables

Oliver - website transition

• Tried importing the News item and then stumbled into nightmare of html from work imports. Think of transferring last 2-3 years of news by hand into the system.

• Do yearly dump to PDF of news items.

• Make sure this is ok with Jared and note it as a policy.

• docs.ddialliance.org waiting for DNS change

Product section

• What is going where and how is this organized

• the doc site will contain information for people technically implementing

• Web will have informative text content for understanding individual products. Add links to key product content:

  • Technical/Implementation button

  • How to make this visual being able to use useful glif/icons

  • Just waiting for the new DNS update

Presentation proposal for EDDI on Roadmap

• Updating Roadmap (priorities, timelines, modifications)

• Next week review Roadmap and finalize submission - look at the roadmap in the meantime https://docs.google.com/spreadsheets/d/1b390D4CpPXqtqi7-e5GhrvWdHbNEG697/edit?gid=728820206#gid=728820206

• Other submissions to EDDI:

  • Darren - CV platform

  • Dan/Jeremy - Colectica

  • Oliver - Colectica

ZOOM SUMMARY (edited)

Meeting summary for Technical Committee (08/22/2024)

Quick recap

The team discussed issues related to payment processing and the need for a new management system, with a focus on using Hubspot's American side. They also reviewed the roadmap for upcoming projects, including the Achim's project, CDI timeline, and the need to update internal links. Lastly, they deliberated on the organization and layout of content on their website and Hubspot pages, and the importance of managing ongoing tasks.

Next steps

• All team members to review the roadmap document and provide comments on priorities and changes needed for the coming year before the next TC meeting.
• Dan to work on implementing icons or glyphs for common elements (e.g. documentation, downloads) on the product pages once the DNS entry is updated.
• DDI team to finalize the product section organization and content flow between the website and technical documentation.

Summary

Payment Processing and Roadmap Discussion
Wendy and Jon discussed issues related to payment processing and the need to find a new way to manage it. They decided to start using the American side of Hubspot to resolve the payment issue, with Jared's assistance. Darren had downloaded all necessary files to rebuild if needed. They also discussed the need to update internal links and identify moved documents. Lastly, Wendy presented a draft roadmap for the upcoming year, which would be updated online for priorities, timelines, and modifications.

Project Timelines and Database Import
The team discussed the roadmap timeline requirements for the CDI project, with Arofan's funding request for $9,000 (setting up the pipeline was part of the request and will be prioritized by the CDI group). The Achim is back on September 11th, and is a key component for this work. The CDI timeline included submitting a package for voting by September 20th, with a webinar planned for October 3rd.

Oliver and Darren discussed the process of importing a database and considered transferring the last two to three years of news into Hubspot. The CV update involved a request for DNS change expected to be functional within 48 hours. Darren planned to make changes to the home page after the redirection from the control recoveries Page was complete.

TC's Roadmap and Prioritization Discussion
Wendy presented a roadmap for TC work and asked for input on what needs to be expanded, changed, or prioritized. Wendy noted that the last cycle of certain product developments would be completed this year. Wendy also mentioned the need to shift focus to tools for assisting with usage and production management. Wendy asked for feedback on prioritizing tasks for this year and identifying any projects that can't be dropped.

updates regarding web site, Hubspot, and docs site.

Wendy and Darren discussed the ongoing work on the Hubspot and the need to reset it with the US side due to address-related issues. Darren confirmed that he had captured all the content to prevent loss. An issue with the docs site was raised by Dan, as the DNS still hadn't been added to the site. (Note this has now been accomplished). Lastly, Wendy brought up the product section, which she and Darren had been working on, and proposed to discuss its progress and vision in the next meeting.

Website Content Organization and Layout
Wendy and Dan discussed the organization and layout of content on their website and Hubspot pages. Wendy expressed a need for a clearer understanding of the flow from website pages to the options set up on the other side (docs and github content). Dan explained that the site would be for people wanting to learn more or technically implement one of the products, and suggested using icons to indicate different types of content. They also discussed the need to wait for a new DNS entry before making links, and the possibility of adding a page with all the versions of a product. The group also needed to decide what content needed to be included and where.

CDI Project Progress and Roadmap
Wendy emphasized the importance of managing ongoing tasks and the potential acceleration of the CDI project. A polished proposal for Eddie was requested, with feedback on the presentation also sought. The team discussed the CDI's roadmap plans, including automation funding and pipeline setup. Issues with CDI 1.0 and 1.1 versions were addressed, with Jeremy advising against releasing multiple incompatible schemas (CDI-101). The conversation ended without any significant decisions or action items, with Darren, Dan, and Oliver offering their availability for future communication.

THURSDAY
ATTENDEES: Wendy, Oliver, Jon, Darren, Jeremy, Dan

Thanks to Jon for replenishing various caffeine supplies.

Home page
https://144531336.hs-sites-eu1.com/en-us/

Editing page
https://app-eu1.hubspot.com/invite-user/2hS9GVzT8oBGMpNa?lang=en&via=link

Inventory of pages and status
https://docs.google.com/document/d/1DIPnvDMWo6SNxxf7bH4O5cwWCUWkrHL-aDlRNCqVM9M/edit?usp=sharing

Notes for editing guide:
From Website Pages
pulldown More tools [Advanced Menus]
Brings up Navigation menu

Select parent page and hover over white space at right of box to get Action icon
Click on Action

Settings
Change name and title
Update slug on URL to short meaningful NCNAME

Actions:

• Remaining subpages for Learn DONE

• Events - DONE

• CDI review ticket - Jeremy DONE

• Products have been moved DONE (down through product page - version pages being shifted to GitHub location)

• Data cleaning on data driven pages DONE

• Working group presentations to the web site from confluence DONE

• Documents have all been moved (copied) DONE

• Databases have been moved and now drive pages: Tools, Members, Contact (need review and pulling things together) DONE

• Currently importing all announcements (can take 6+ hours) DONE

• 4 automated build pipelines are now in doc.ddialliance.org (ddi-l 4.0, ddi-l 4.0 guidelines document, SDTL and CV) DONE

TO DO:

• wlt - Correcting internal page links from new site to http://ddialliance.org site - Wendy will correct these this weekend DONE

• Testing of new domain

• Review organization/navigation and make known changes at least in Products (TC area)

• Add link to Dan's site on doc.ddialliance.org for product content from the basic product page

• wlt - Go through and change DDI-L to DDI-Lifecycle etc to be consistent (DDI-CDI, DDI-C, Disco, SDTL, XKOS) DONE

• New site announcement to members/users (will complete closer to changeover date) - write Jared a newsletter piece on progress

• Brand/style guidelines - including consistent navigation approach

Wednesday
ATTENDEES: Wendy, Oliver, Jon, Darren, Jeremy, Dan

Thanks to Jon for replenishing various caffeine supplies.

• Received quote from HubSpot and discussed with Jared.

• Worked on issue #36 on DDI-L version 4.0 model, resolved all items in spreadsheet and entered in COGS

• Approved and merged pull request in ddimodel

• Met with Michael and Jared regarding HubSpot, DNS, and database content/usage. Resolved questions

• Resolved some issues concerning HTML page of CVs to remove duplication

• Exploring use of HubSpot features and how to do things like filters - identifying best approaches

• Fixed misspelling of Abstract in DDI-L version 4.0 BETA2

Discussion

• Where different doc types go? GitHub or S3

• GitHub is easier to load, drag, and drop

• Roadmap for moving from hand/semi-hand crafted to automated

• Check with Deirdra on GitHub location

ACTIONS:

• Jon is sending specific email Jared with link to product, quote, and reasoning. DONE

• Dan will follow up with Jared regarding DNS zone change

• Oliver will email Sanda with proposed solution including caveats for version info, and usage DONE

• Write guidelines for updating web site using HubSpot

• Thursday Darren will get some data cleaned and into tables DONE

• Oliver will create a table of tools, members, publications DONE

• Look at mail type functionality so that Jared can use it for targeted mailings DONE

FUTURE TO DO:

• Review examples to make sure they are parsable - moving to GitHub will let us provide a validation process to make sure these are accurate

• Profiles should be community generated but will need in various languages - recommended ways to express profiles

• ICPSR metadata with a JSON schema (look at this to see if there are objects not supported by DDI)

TUESDAY
ATTENDEES: Wendy, Oliver, Jon, Darren, Jeremy, Dan

Many thanks to Jon for supplying not only the rooms but the snacks and most of the the Coke Zero and coffee/tea to keep us all adequately caffeinated.

AGENDA:
https://docs.google.com/document/d/1DIPnvDMWo6SNxxf7bH4O5cwWCUWkrHL-aDlRNCqVM9M/edit?usp=sharing
Content spreadsheet:
https://docs.google.com/spreadsheets/d/1bcvxmwoxUWyhZfTkuR9ZrVtmCxz2mkE8cFYYyjpCLtM/edit?usp=sharing
Dump:
https://drive.google.com/drive/folders/1_imyqyrS59Of25Yz-NNcMYhwvhUkTCK_
Published site (HubSpot):
https://144531336.hs-sites-eu1.com/en-us/

DECISIONS:

• ICPSR has extended move date from Sept 1 to Dec 31 so do not need Plan C

• Complete work as soon as possible - preferably by EDDI

• Use HubSpot- explore upgrade options (limit 5 users, 30 pages in free version)

Discussions:

Choice of software - main point is to get out of self maintained
Distribution of content:

• Static and generated content (admin) on HubSpot, documents on AWS S3buckets - field level documentation generated from GitHub, documents

• Looked at how much needs to be on web and what can be off on doc.ddialliance and maintained on GitHub in terms of products. Need to flatten and provide consistent access.

ACTIVITIES:
Exploring the site dump for content specifics

QUESTIONS FOR MICHAEL:

• Request to change DNS for doc site

• Create a single table with all the values for membership and other data bases

• What is the difference between Publications and Bibliography?

ACTIONS:

• Darren will go in to HubSpot to check on functionality at different levels for databases, contact submissions, use for internal as well as external uses of database content. DONE

• Dan will set up Route 53 zone and send email to Michigan regarding actions needed DONE

• To set up the DNS for the technical documentation website, we need to request from ICPSR to delegate NS for http://docs.ddialliance.org to: (DONE)
  http://docs.ddialliance.org . IN NS ns-1840.awsdns-38.co.uk.
  http://docs.ddialliance.org . IN NS ns-1071.awsdns-05.org.
  http://docs.ddialliance.org . IN NS ns-901.awsdns-48.net.
  http://docs.ddialliance.org . IN NS ns-421.awsdns-52.com.

• Darren is setting up page templates so content of static pages can be loaded DONE

• Send Jared table of members as excel to see if it contains all that he needs. Is there additional information that needs to be exported (example is member email addrss maintained separately?) DONE

• Entered all first level pages under Learn (DONE)

• Need to check for links to forms etc that would need to be changed

• News and Members from database (can redo if we need to clarify) DONE

• About to do same for publication (DONE)

• About sections DONE

• LEARN first level pages and sub-levels entered DOE

• Moving published product documentation onto doc.ddialliance (will create landiing page) DONE

• Mirroring existing site (Plan C) DONE

• Membership navigation structure DONE

• Created base pages DONE

• Publications (need to chat about) DONE

• Work on styles started

• At limit for pages at no cost, HotSpot will give us a couple professional tools for a couple of weeks DONE

• Membership pages DONE

• Added Learn, Membership, Events, Publications, About to inventory spreadsheet completing sub-page listings (left off straight links to existing pages on hierarchies of other sections, documents, or other sites DONE

CHANGES TO PAGES

• Membership entry page content changed to a drop-down

• Lost brown/blue/green color boxes (for consistent item types like "download", "XML entry point", "Field Level documentation",etc. will look at adding icons)

ATTENDEES: Wendy, Jon, Oliver, Dan, Jeremy, Darren, Jared (guest)
Regrets: Flavio

F2F and Web site planning

See https://docs.google.com/document/d/1DIPnvDMWo6SNxxf7bH4O5cwWCUWkrHL-aDlRNCqVM9M/edit?usp=sharing

ACTIONS:
Jared:

1. Updated dump of database - completed 2024-08-08

2. Functionality of administrative section

3. Meeting time with Michael - set for 2024-08-14 8:30 EDT, 13:30 London

Wendy: (Notification to Content Managers)

1. Hold on updates during next week (Training, Admin, Marketing, Product) - completed 2024-08-08

Text of email:
Chantal, Kathryn, Jon, Jared, Hilde, and Arofan,

I am writing to you as content managers on the http://ddialliance.org site. I have included Hilde and Arofan as they are preparing DDI-CDI for a vote in September and may need content changes in the website regarding this.

The Technical Committee will be beginning the process of moving the http://ddialliance.org site from ICPSR to the UKDA. ICPSR will be creating downloads of the site content between now and Tuesday 13 August. We will then be creating a prototype of the new site. We will be running parallel sites while we check out the accuracy and stability of the new site. We would like to keep any changes to an absolute minimum for a period of time. We should be able to provide an estimate of this time period by the end of next week.

To that end please:

1. Do not make any changes to the current http://ddialliance.org site before August 20.

2. Follow guidelines that the TC will provide before August 20 regarding any necessary changes made for a period of time following August 20.

3. If you need to make content changes before August 20 or during the limited access period defined in the guidelines we will provide, please contact me to ensure that changes are reflected on both sites

4. We understand that upcoming events such as the CDI vote will require some changes as well as needed announcements. We will keep this period of limited change as brief as possible. We simply want to ensure that content changes are made to both sites in a consistent manner.

Thank you for your help with this move,

Use of Zoom Summary
Jared forwarded the summary from last week
Wendy has sent to members for review and comment
Looks useful, will need to configure meeting set up to have summary sent directly

Post meeting:
Jared raised 2 additional issues in an email which will be added to agenda outline

1. Web hosting expenses. What will they be and through which provider. If above a certain amount, I may need to vet the provider through UM.

2. Administration. I'd us to keep the number of people who can make direct edits on the site to a low number. Prior to the clean up a few years ago, we had 70+ users with edit permission. Most hadn't logged in for years (and I removed their access due to security risks), but the disparate editors sometimes made for dislocated content. My recommendation is to have the TC edit the Products section. For the other content (mainly involving Training and Marketing), I suggest requests work through me. This helps make sure we have consistent messaging. Thoughts?

ZOOM SUMMARY (edited)

Meeting summary for Technical Committee (08/08/2024)

Quick recap

The team discussed upcoming website changes, a security incident involving the University's website, and the issue of language repetition in HTML output. They also planned for the organization and storage of documents in the new 'docs.ddialliance.org' website, and the need for improved organization and descriptions for their working groups. Lastly, they arranged for transportation to UCL for upcoming meetings and discussed the transfer of the current site's content to a new database.

Next steps

• Jared to provide an updated database dump of the current website content to Darren.
• Jared to compile a list of current administrative functionalities on the website for the team.
• Jared to schedule a meeting with Michael (web team) for the following week to discuss potential needs.
• Wendy to send notification to content managers about holding off on website updates during the transition period.
• John to send his phone number to the team for emergencies during the London meeting.

Summary

Upcoming Travel, AI Tool, and New Team Members
Jon, Wendy, Dan, and Jeremy discussed their upcoming travel plans and the use of a new AI summary tool. Wendy expressed difficulty in accessing the DDI Alliance Mail to share the summary, and Jared offered to forward it.

Website Changes and Emus Discussion
The main agenda was then addressed - plans to announce upcoming website changes to members and users, gather feedback, and determine rollout strategy. Wendy shared a document outlining these plans and asked Jared for his input on prioritizing next steps.

University Website Security Incident Discussion
Jared discussed a security incident involving the University's website, where malicious ads were injected. The University's Information Assurance team, responsible for a major incident a year ago, wanted to take the site down due to the security incident. However, Jared disagreed and managed to get a commitment from the team to keep the existing site up until December, with a possibility of minor internal shifting. Wendy questioned the need for a backup plan, given the issues with the current setup and functionalities, and the ongoing work on the prototype.

Addressing HTML Repetition in RDF Release
The team discussed the issue of language repetition in the HTML output of the CV group, which was identified as a potential problem for the upcoming RDF release. Oliver and Wendy had been exploring the possibility of transforming the HTML output to eliminate duplication, a solution preferred over holding up the entire chain. Despite concerns about the aesthetic of the output, the team agreed that the priority was to have the RDF resolution system in place for the CDI release. The team planned to further discuss and resolve the issue in their next meeting.

News Item URL Structure Discussion
Jared and Darren discussed the potential changes to the URL structure of the news items on their website. Jared mentioned that there were over 50 news items, and Darren was unable to access the site to confirm the details. Oliver suggested setting up redirect rules if the URLs did change. There was also a discussion about the possibility of only importing news from the last year to support archives, but this would mean losing older content. Darren agreed to investigate the redirection issue, and Jon checked if the current URLs were supported by Hubspot.

Improving Member List and Publication Functions
Jared discussed the functionality of the Member List section and expressed interest in improving its display capabilities. Darren suggested that 80-90% of the new prototype should be completed within a week for feedback, with the remaining 10% to be addressed in the following weeks. Jared also brought up the topic of the publication section's functionality in the new site. Wendy requested Jared to list any additional functionalities to better understand the current system and identify any gaps or issues.

Organizing Documents on New Website
The team discussed the organization and storage of documents in the new 'docs.ddialliance.org' website. Jared, Darren, and Wendy discussed the need for a balance between HTML pages and PDF documents, with the intention of providing users with both easy-to-access HTML content and the security of PDF backups. They also discussed the potential for storing these documents in an S3 bucket, rather than internally on the website. The team agreed on the importance of having a clear and intentional structure for the new site.

Improving Working Group Organization and Communication
Jared, Jon, and Wendy discussed the need for improved organization and better descriptions for their working groups. They agreed on the importance of having text, not just links, for easier navigation and decided to move forward with the plan to transfer content while keeping functionality. Wendy proposed that a placeholder for an upcoming change be included in the next newsletter, with further details to be discussed later in the year with working groups. Wendy also requested that future communications be copied to Oliver, who is now the vice chair, and mentioned that she and Oliver would be reviewing the distribution of tasks within the committee. Lastly, Wendy requested a list of functionalities for the administrative sections from Jared for the following week.

Database Dump and Site Updates Strategy
Jared will ask Michael to provide another database dump for the current site's content, which will be sent to Darren. The team will discuss the best time for this transfer, likely on Wednesday. The team also agreed to hold off on making updates to the site until after the switch, with Jared suggesting he might create new content items instead. The team will reassess their approach after the prototype is up and before finalizing the site.

Transportation, Arrivals, and Notifications
Wendy and Jon discussed transportation arrangements for themselves and the others attending the meetings at UCL next week, with Jon recommending the Elizabeth line. Darren confirmed his arrival time on Tuesday morning. Wendy assigned an action for Jon to send emergency contact details. Wendy also assigned an action for herself to send a notification to the content managers and remind Jared about updating the database functionality and scheduling a meeting with Michael.

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

Codebook - Pull Request 41

F2F
Jared's email
This is to check on the status of the web site migration. When do you plan to switch it over to the new host? When can we turn off the ICPSR-hosted site? Will we retain the same URLs at the new hosted site? Do you need our web team to be available for a few hours during the planned switchover? For content transfer, is this inventory still accurate?

I had one to-do relating to formalizing an agreement about who is doing what for web and resolution support. I recently spoke with the UM General Counsel office about creating legal agreements for web site hosting, maintenance, and support, as well as supporting the resolution system that has been set up to support CV and RDF vocabulary resolution. While we do not need details to create a draft for the web site actions, can you please specify the specific tasks and deliverables for supporting the resolution system?

I'm out next week without access to email or phone but will be back on the 5th. Can we talk then? I'm especially interested in how the Secretariat-owned sections, like Get Involved, Publications, About will function on the new site. I'm also interested in communicating these planned changes to the wider community.

Notes from CDI for TC:

Lifecycle using CDI as a bridge standard to SDMX
RDF expressions of DDI versions are moving forward
See if we can get Eurostat to look at the RDF from Lifecycle
UNECE is having a meeting 3rd week of October with side meeting of CDI/SDMX alignments
Eurostat has a conference in March NTTS (submission date 30th of September)
https://cros.ec.europa.eu/dashboard/ntts2025

CDIF
http://Schema.org in the middle pointing out to different things
Handling handoff between CDIF and DDI is CDI
There hasn't been a discussion of Products that should be involved

TC is accountable for some outreach activities and we need to coordinate this better with Scientific Board and other outreach activities. There should be broad support for the Product Suite with targeting taking place where appropriate.

FROM ZOOM SUMMARY (edited)

Meeting summary for Technical Committee (08/01/2024)

Quick recap

The team addressed various issues related to the code book, the website's hosting location, and the potential risks of transferring content to a functional site. They also discussed the need for improvements in the content management system, the display of language labels in CV groups, and the organization of documents on the docs.alliance.org website. Lastly, they touched upon upcoming developments from UNECE and Eurostat, and the importance of transparency and consultation with the technical committee.

Next steps

• Oliver to implement corrections for the HTML and SKOS files for the controlled vocabulary site by the end of the London meeting week.
• Wendy to write to Jared expressing that it's unreasonable for ICPSR to move the deadline for the site migration to September 1st with such short notice.
• Dan to add a task for the London meeting to create a static version of the DDI site as a backup plan.
• Jon and Darren to evaluate and provide feedback next Thursday on the feasibility of moving the majority of the site content by the end of August.

Summary

Addressing Code Book Issues and Feedback
Wendy addressed several outstanding issues related to Codebook. Wendy clarified the meanings of certain attributes, corrected a misspelling of 'orchid', and improved the formatting and clarity of the documentation. Wendy also planned to review codebook tree issues from Knut. Dan and Oliver provided feedback and suggestions for the commit message when merging the changes. Wendy thanked them for their input and agreed to implement their suggestions.

Website Hosting Change and Challenges
Jared from ICPSR notified the team that due to recent security issues, they need to move their website from the current hosting location by September 1st, much earlier than the previously agreed December 2025 deadline. The team discussed the challenges posed by this shortened timeline and the need for a temporary hosting solution during the transition period. Dan and Jon suggested pushing back on the new deadline as unreasonable with such short notice, but also proposed discussing interim options like a backup site with Jared and Dan in the next meeting.

Site Transfer and Backup Plan Discussion
Jon, Wendy, Dan, and Oliver discussed the potential risks and solutions related to moving the majority of their site over to a functional site by the end of August. Jon expressed his belief that the site's content could be successfully transferred, but highlighted the challenges with DNS and other related issues. As a backup plan, Dan suggested creating a static version of the site. Oliver agreed, noting that the only interactive part of the site was the search functionality, which could be removed. Jon proposed directing their concerns to Jared, suggesting an extension as a more reasonable solution. Wendy agreed to draft a letter to Jared, with Jon's review for accuracy.

Addressing Duplicate Language Labels
Wendy and Oliver discussed the issue of duplicate language labels in the HTML and SKOS files for the controlled vocabulary site. They agreed that this duplication was unintended and needed to be addressed, with potential solutions including transforming the SKOS file. They also discussed the availability of multiple language versions in the HTML for their publication plan, with Oliver explaining their current setup using secondary HTML pool methods through the REST API. Wendy acknowledged the convenience of having multiple languages, and they agreed to consider whether they wanted to adopt the same approach.

Addressing Content Management System Issues
Oliver and Wendy discussed issues related to the use of a content management system. Oliver explained that the system generates files each time a publish action is performed, rather than on the fly. He also pointed out that the current versioning system for languages was causing problems. Wendy expressed concerns about the time it would take to make changes, to which Oliver suggested two potential solutions: making corrections during his trip to London and starting a new service without the current system. Wendy agreed to these proposals, emphasizing the importance of getting the project up and running.

Addressing CV Groups Language Label Issue
The team discussed the issue of language labels not displaying correctly in the CV groups, as raised by the CV group. Dan expressed his opinion that this issue doesn't affect the usage and suggested improving the rendering. Oliver agreed but noted that users might prefer to wait until the error is fixed before setting it to hold. Wendy proposed a temporary fix and prioritized it, as it was only for a limited time. The team also discussed the need for a flag to notify users of errant duplication in multiple languages, which Wendy suggested would not significantly impact overall usability.

docs.alliance.org Website Structure
Wendy and Jon discussed the organization and presentation of documents and specifications on the docs.alliance.org website. Jon suggested that the site should provide options for users to make decisions and that specifications should have a presence on the main site. They also discussed the potential for confusion between the docs and main sites, and the need for clear guidelines. Dan added that the new system should accommodate automatically generated artifacts from specifications. The team agreed to further clarify the site's structure and content.

Upcoming Developments and Transparency Concerns
Wendy discussed upcoming developments from the UNECE and Eurostat, particularly regarding Lifecycle v4.0 and the use of RDF. Wendy also mentioned an upcoming conference with a submission deadline of 30th September. Jon expressed concerns about the lack of transparency and consultation with the technical committee regarding these initiatives. Wendy agreed to discuss these issues further with Oliver, the new vice chair, and to consider the committee's involvement in future activities.

ATTENDEES: Wendy, Dan, Jeremy, Adrian Dusa (guest)
Regrets: Jon, Darren, Oliver, Flavio

Codebook pull request

approved, merged, related issues closed

Codebook issue #18
Adrian Dusa will join the meeting for this discussion. Please look at the issue prior to the meeting.
https://github.com/ddialliance/ddi-c_2/issues/18

ADDED to Issue #18 by Dan: At this week's TC meeting, we discussed the current attribute documentation and if it makes sense to add explicit documentation at the attribute level such as

<xs:attribute name="..." ...>
<xs:annotation>
<xs:documentation>...</xs:documentation>
</xs:annotation>
</xs:attribute>

Adrian will provide examples of end products for suggested changes. These will be vetted with Jon regarding docbook HTML documenation creation. Timing this for the last set of structural changes to be made to schema prior to presentation for vote. Goal is to provide consistency in presentation for ease of reading and to better support capture and transference of documentation to other tools for codebook automated maintenance or new and existing codebook tools. May want to run this by Mehmood for WorldBank tool and Tools group (at least Olof for his tools).

DDI-L 4.0 BETA2 issues - continue to locate previous discussions and link or copy to issues. Whatever we can get done prior to F2F is great but at a minimum issues for discussion should be clearly defined to have a focused discussion.

Web/F2F prep
Jon has added some notes on doc.ddialiance.org organization as well as on the products section
Please look at these and comment or add to. One issue may be looking at when we get into reorganization of section content. For products some is being done before the F2F as we discussed in in March. Other reorganization may need to take place after the F2F within the context of overall revision of the web site. The primary goal of the F2F is to lift and move the current ICPSR site content and make sure there is no loss. Organization of new areas like doc.ddialliance.org are definately on the F2F agenda as we want those well organized and usable in September for new publications.

https://docs.google.com/document/d/1DIPnvDMWo6SNxxf7bH4O5cwWCUWkrHL-aDlRNCqVM9M/edit?usp=sharing

CHECK out the AI Companion and Start Summary for assistance with minutes - play with this next week

ATTENDEES: Wendy, Jon, Dan, Flavio, Jeremy

F2F preparation
Face-to-Face
https://docs.google.com/document/d/1DIPnvDMWo6SNxxf7bH4O5cwWCUWkrHL-aDlRNCqVM9M/edit?usp=sharing
Website Management
https://docs.google.com/document/d/1ihi4UlL4calygWp1wgFuO8Npqh_xPvtl4evAtXB-rEQ/edit?usp=sharing

Web pages

• Added page on filing issues and product level pages as per discussed earlier in the year

• Overview of what's in the suite and comparison of - rename this

• Contents listed on product page for each version (should list occur here or just link

• Can this be flatted out more

Codebook

• Decide layout plan (indention, line spacing) and prepare validation process in GitHub

• Delay cleanup of structure until last step

ATTENDEES: Wendy, Jon, Flavio, Dan, Jeremy

Codebook pull request - merged

DDI-CDI next steps -
Review processing issues - none filed
Verify URN for version 1.0 [Darren and Arofan] generic ddialliance.org/specification/DDI-CDI will be used for the general project page with links to each version
Check with about the listed issues

Face-to-Face meeting prep
Use next 4 meetings to ensure we have a clear listing of steps to complete during F-to-F
Includes getting a DDI-L v4.0 BETA2 out the door

4.0 critical issues in preparing BETA2

• Ordering

• References extension

Documentation websites on GitHub get it on CI automation -> docs.ddialliance.org
Process for putting all other docs on the documentation website - let DDI-CDI
There may be a standard Header/Footer for common look and feel

FUTURE AGENDA ITEMS:
Face-to-Face meeting prep
Website prep - get dates

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

REGRETS: Darren

As of 1 July 2024 Jon Johnson will step down as Vice Chair of the Technical Committee. Oliver Hopt will serve as TC Vice Chair from 7/2024 through 6/2027.

Codebook pull request

• Approved and merged - covering references to DDI CV’s, typos, missing documentation

Codebook - Simple Text Review

• Approved 8 identified changes out of 86 simpleTextType that seemed logical (respUnit as parallel to anlyUnit) or where known non-DDI CVs exist within a discipline or organization (imputation types, availability status)

• Make those changes and retain spreadsheet for future Codebook Working Group

DDI-L v.4.0 BETA

• Priorities are ordering and internal enumeration issues

• Many issues administrative; Jon will add content to these

• Face-to-Face will be 3 days and we should be prepared to spend on BETA work to the extent possible

ACTION

• Wendy will provide a google doc to list technical and content management issues for the Alliance website https://docs.google.com/document/d/1ihi4UlL4calygWp1wgFuO8Npqh_xPvtl4evAtXB-rEQ/edit?usp=sharing

• Please add to this document with additional issues or expansion of listed issues

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

Codebook pull request
Merged license update issues 97 and 93

Codebook review of simpleTextTypes
Issue arose in adding in documentation on existing DDI CVs of possible simpleTextTypes that should be conceptType or conceptualTextType (ex. “software”

ACTION:

Create annotated list of these on spreadsheet and send out
send out to SRG list to open for other to comment in open google doc if comments needed
Wendy do this and send it out

DDI-L V4.0 BETA issues and workplan
Pull request adding license (issue 32) merged
People should review issues and work on one of their choice
It would be good to have content changes (as opposed to administrative issues) addressed by August meeting so that if there is time we can move on getting BETA2 out for review.

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

TC Chair and Vicechair for July 2024 - June 2027
Main concern is that the role is too much. We need to pull out Lifecycle and Codebook and look at the workload overall to spread out among the group.

Face-to-Face meeting
Thanks for your responses. I'll let you know the preferred times although we still need to adjust to the availability of the hosting agency(s).
13-15 August

Work on DDI-L V.4.0 BETA2
scheduling this work given people's availability
Preferred approach is to just starting to put it on the schedule
Marking the properties that need explicit ordering for RDF serialization

Codebook - please respond to the request for comments on the most recent issue. I will submit the pull request around 6 pm CDT Wednesday. High level documentation - outline
Pull request merged. One typo found DDICODE-540. Enter remaining schema updates DDICODE-540, 97, and 93. Change merged IN REVIEW items to closed. Start documentation issues that are related to high-level documentation.

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

Codebook pull request
check vocabID or vocabName?
lines: 2558, 2797, 4336, 4574
Follow-up findings: vocabName is not an attribute (vocab); vocabID was added to replicate content from DDI-L. Documentation on vocabID was updated to clarify the use.
https://ddi-alliance.atlassian.net/browse/DDICODE-539

Face-to-Face Meeting
Oliver not available in July 31st of July is first day available
Flavio remote availble in July/August
Dan
Begining of the week of 22nd OK
Begining of August 1-2nd goood
August OK except middle of month weekend
Poll - for availability

CDI review
Extend to end of June - email everyone with a prod to finish and file their work

Glossary review
Nudge to Training group people

Feedback from SB and EB meetings
no additional comments

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

Update on CV and RDF resolution system
Overview of RDF system (on wrong system waiting for switch of DNS by Michael)
Showed timeline quiet launch 17-June
Formal TC approval to go ahead and go live on the 13th
Not all target languages come through in the same manner - Oliver working with algorithm
UKDA will take responsibility for maintaining this, but we need to formalize this - check with Jared on what is needed
XKOS is ready to go - only have a turtle would JSON be useful? Check with Franck

ACTION: Darren will talk to Franck next week regarding JSON for XKOS

DISCO is not yet published
It needs to be flagged that its not published
Can we put something out on the list
Are people using it? Would it be helpful
Who would be maintain - working group
PRIORITY: We probably shouldn't say its a w3c spec but it hasn't gone through
PRIORITY: We should update template to make it DDI - It is in the tracker as completed in 2019

Update on DDI-CDI targeted review
Sent request to see who is covering what...no additional responses yet
Flavio - UML/XMI and is checking on syntax rep review

Update on Glossary review
Several issues filed (12 have been filed, Training Group people have also volunteered)
ACTION: Follow up with working group on publication (web plus?)

Codebook
new pull request - Dan will clean up Wendy's mess and we'll re-commit content for pull-request
DDICODE outstanding issues - updates on 93 and 97 Darren will look at 95

July 4th CANCELLED due to British Elections

ATTENDEES: Wendy, Darren, Oliver, Dan, Flavio

Web pages/ site plan
https://docs.google.com/spreadsheets/d/1bcvxmwoxUWyhZfTkuR9ZrVtmCxz2mkE8cFYYyjpCLtM/edit?usp=sharing
From Jared:
What would be useful is to make a final decision whether the Technical Committee is committing to supporting the website infrastructure or if we should go with the vendor. If the former, will you support all functionality currently on the site or just portions? At a minimum, I need a place to post announcements, manage a membership list, and manage/edit all pages other than the /specification sections.
There's other functionality on the site, like the Bibliography or the Glossary or the Tools list that are nice but maybe could be hosted separately. Those are also decisions we'll need to make.

Discussion:

• Could support static or file content in something like S3 buckets

• COGS stuff could be bundled up as static content and hosted on docs.ddialliance.org

• Don't forsee any major problems in doing a serverless website that looks nice and bounces over to an object storage

• Could do a test migration in July during a 2-day meeting

• Can set up S3 buckets to test

• Tools etc. could be a non-database filter system

• Hotspot has the management system build into it that should support Jared's editing needs

• TC taking this on would save the transfer fees of the outside vendor. We would need to look at ongoing maintenance. Zero risk as we can build this as a parallel system this summer, test it out, and institute further changes following that.

• Do need to make sure we have document and project page organization determined so that new products and versions can be assured of URL consistency for linking purposes

ACTION: Darren will write to Jared

Scientific Board Plan
Clarified a few points. Will get final draft for tomorrow

CV publication

• Basically there

• DevOps team at Michigan have made the changes they needed to make

• Working with CV group to update static content on pages

• Problem of duplicate language (again) in the HTML

• CESSDA is not seeing the problem - if they won't fix we could filter out duplicates as an interim response

• Darren plans to go live the week after IASSIST if this works with the CV group

• Meeting on Monday to finalize the ontoloty access

• Oliver has discovered source of duplication: CESSDA has put an all of the versions together because they use a select bar. The Rest API ends up with 2 versions of both

• We could switch to this display but it may be complex for the user

• The CESSDA change dropped out some of our requirements - do we drop our requirements or ask them to make the change. We don't want what has come out with multiple versions (different versions) in different languages.

• We are concerned with the RDF version and we need to go live with this. The HTML is still a problem

Codebook outstanding issues
DDICODE-93
DDICODE-95
DDICODE-97

Darren will look at these

Presentation on DDI-L .v4.0BETA - who presents
Will sort this out off-line

Future agenda:
Chair, Vice-chair (3 year term)

ATTENDEES: Wendy, Jon, Darren, Dan, Jeremy

Web pages -

General:

• Want to control the website and not have it jobbed out

• There is static content that could be usable but not necessarily optimal

• Get it over and done and implemented and then think of the redesign

• Need to get basics done first (lift and shift)

• Opportunity to move to keep it simple then talk to groups involved (Training, TC, Publications)

Products:

• Putting up stuff around infrastructure and pipelines

• Top level URLs for the products will be hard coded or redirected

• If CDI has specific requirements they need to write them down

• This seems the obvious stuff to write this down

Document site:

• Timing of when we are going to split the document move to doc site

• Identification of documents should be part of the new site map

• Do we retain the static pages as just the publications and say the docs are over there (old docs)

• A page for product on the site but all in-depth documentation on the doc site

• Useful to have a profile of what goes on the doc site for future additions and help to groups in identifying what goes where

ACTION ITEMS:

• Darren and Jon will draft up a basic skeleton of the site map to kick against

• Add to next weeks agenda

• Known static content changes should be made before TC f-to-f meeting (ACTION: Wendy)

TC report to SB
Comments noted on draft

Update on current review work
I will continue to send reminders to reviews of both products during the review period

• Glossary List

  • Review underway

  • Several volunteers from Training Committee

• DDI-CDI Production:

  • Plans for sustainability of the standard; once its done in EA what is the pipeline (Jon will relook at the documents)

  • Olof - JSON

  • Pascal will begin in early June, may need extension

  • Dan - RDF output, looking primarily to see how they were transforming UML into RDF; special semantic relationships like traces in UML to identify patterns - how is this translated to canonical UML and then to syntaxes (are these just there to support their development of the model? this should be clarified)

Codebook (please look at before next week)

DDICODE-93 License - more detailed values for type attribute
DDICODE-95 https://ddi-alliance.atlassian.net/browse/DDICODE-95 deprecation - URI attributes needed
DDICODE-97 move license element to useStmt

ATTENDEES: Wendy, Jon, Oliver, Dan, Jeremy, Flavio, Christophe, Olof
APOLOGIES: Darren

Scientific Board Strategic Plan

[note Flavio and Dan are elected members on the SB. Wendy is ex-officio]
Flavio noted a couple of issues he'd already added
"horizon scanning capability"
"more robust" more of a clear source of truth

1.4 W3C and explore - RDF representation preparation in 2024 - why would we want to give away the variable cascade to another organization
Increase visibility, not "give away" needs to be more explicit

1.6 no date so when is this supposed to be worked on? non-open source like Colectica - what does it mean? The notion that we are working with commercial vendors and make no mention of those we currently work with. What exactly are we trying to develop? Work with related software (analysis tools) regarding input/output support?

2.2 we don't have an activity defined as such, what is in 2024? Clarify what this is mean here? architecture of content or of repository. Starting when?

2.3 addition of SDMX and HLG to this group specifically or as part of whole DDI interoperability. What do we mean by this in terms of organizational level?

2.4 The example is about domains not geographies but domain areas. Awkward, examples do not relate to geographies.

2.5 Progress toward ISO certification (we started, why is this 2025? What is meant by progress. More details - contact continuation, paperwork,

GENERAL: of strategic plan to prioritize and focus work on specific areas. Concern there is too much for too many. Who is going to do this.

3.1 TC is working on in terms of organizing documents and publication

3.2 difference between 3.2 and 3.4?
Maybe some collapse into a broader infrastructure for development, management, presentation

GENERAL: Verbiage is abstract making it difficult to differentiate and make sure that different aspects are identified as sub-bullets

Omitted support of DDI Codebook 2.6

3.8 don't understand what this means (modularity within a product), but between products? Why is the example is a provenance model.

Discussion on user mailing list (conceptual, and reference variable) was the actual issue we would face with 3.8. things differ between products and there are different implementations in various products. Need for metamodel to understand what is found in multiple products, but varying implementation. Example of metamodels (Groups).

Need both metamodel to understand differences, and in some areas a single mullti-use content.

Suggestions in the scientific model that haven't been discussed. They seem to be arising from a minimum number of sources

"Let's do a provenance model" opens up a can of worms. No background discussion. There is a process raising topical rears and pursuing their development across products in one way or another.

HOLES?: Lack of content regarding how to use DDI suite together. (maybe related to 2.6) maybe expand to include 2024?

ACTION:

• Wendy will add notes to document

• Start list of content for report, next year priorities for TC; send out to get comments before next week

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

Newsletter submission
Thank you for XKOS work on publication process
Alert people to recording on Lifecycle 4.0 BETA and continuing work

TC report to Scientific Board
Web page support through AWL
Infrastructure
Codebook
CDI review
4.0 BETA continue to finalization

Glossary Group document publication
TC to look at in terms of technical review
Check in Glossary that its DDI
Hayley get a few Training people to look at
Christophe will talk with INSEE folks regarding clarity
Month deadline

https://ddi-alliance.atlassian.net/wiki/spaces/DDI4/pages/2790359041

DDI Lifecycle github issue
r:ManagedMissingValuesRepresentation at RepresentedVariable level · Issue #38 · ddialliance/ddimodel

Rather than think of the specific item raised here
What is the purpose of the represented variable
If its available it should be in represented variable
there is a difference between practical use cases which might not be the dominant ones
Issue is primarily around missing values and problems of how coding or options change from capture through processing to instance and physical store differences
Currently clear change from represented to instance is going from universe to population (spatial temporal specifications)
Different sorts of data throw up different problems
One of the strengths of the schema it is quite directional (this can also)

ACTION: Wendy enter this discussion on #38 (DONE); others should add comments on role of RepresentedVariable or other points as needed

NEWS:
Guillaume is returning come September

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/*
 https://ddialliance.org/learn/markup-examples-by-version?field_ddi_product_tid=All
o Also move relevant referenced items under https://ddialliance.org/sites/default/files/*
 At the root level under http://ddialliance.org .
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.

https://docs.google.com/spreadsheets/d/1y54OKTmJeSV3YwxR6RBa7yJyHvD8P1drjPmG4C2vZoM/edit#gid=517461823
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: https://docs.google.com/document/d/111V1om6vbaJQCgxYI_znA03xDWW9HwW0iMGHxNVVnHU/edit?usp=sharing

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

ATTENDEES: Wendy, Dan, Oliver, Darren, Christophe

AGENDA

Resolution system

CV system

• Access to https://github.com/ddialliance/ddi-cv-platform (am hoping that Oliver will be at TC tomorrow).
  All is in hand

• Misalignment of version numbers in https://github.com/ddialliance/ddi-cv - logged at https://github.com/ddialliance/ddi-cv-platform/issues/1

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

ATTENDEES: Wendy, Dan, Flavio
POST-MEETING WRAPUP (due to forgetting US change to DST): Jon, Darren, Oliver, Christophe

Review of approach to issues 8, 23, and 32:

• Issue 8: (spreadsheet has been added to issue)

  • Identify good canditates for conrolled vocabulary

  • Group itesm need either documentation of definitions of types or use a controlled vocabulary. This is true of internal enumerations currently containing documentation.

• Issue 23: (spreadsheet has been added to issue)

  • When versionables reference other versionables looking for order needs - assigning of contents is required or used

  • DISCUSSION: How explicit order gets injected - clearly needed in some serializations but XML has two camps (order implied, order not implied)
    First step is identifying where order is needed

Additional Topics:
ISI presentation:

ISI do we want to propose something on DDI like last year in Ottawa?

Does TC want to send something - IPS

We have 3 weeks - kick around an idea for a topic

Something beyond use cases

Parts of DDI - multiple serializations

How content fits together and can move between products

3-4 people with or without discussant

XKOS:
Best Practice ready to go so look for email on that

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

Codebook

• Pull request has been amended and content is now correct

• Looking forward, the concept/conceptualText will be posted immediately following the resolution of the current pull request

• This will be followed by the remaining issues which are more targeted

ACTION ITEM:
Dan will note items that are NOT documentation change so they can be reviewed next week

DDI-L 4.0 Beta 1 Issues

• Another beta the middle or end of April after gathering COSMOS feedback

• An issue on representing sentinel variable values in Represented Variable

• All new content issues should go into GitHub. They will be tagged for releases.

• This will also allow broader discussion of content issues in clearer way than we have been able to do before.

ACTION ITEMS:
Wendy:
#36 - go back and pull together the earlier discussion of dealing with extended reference and review current need for continued use of this content
#8 - review enumerations as converted to CSV and conversion to outputs
#23 - locations of ordered attributes
Jon:
Administrative documents - add content on #16, #17, #30, #31, #32, #33, #34

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

Webinar review

• A lot of people who we seldom or never seen

• Good suggestion:

  • Guidance on pull requests

  • We can set up templates

  • Contributors guidance document

• Missing documents

  • What is the model

  • Master?

  • Development version

• In terms of code the past published specifications can be compared

• Between 3.2 and 3.3 we could do a dif but we can't track between 3.3 and 4.0 because each generation is structurally different (dependent on mapping and change documentation)

• The ability to track individual changes

• How do we want to do this? If we publish 4.0 as a package

  • Track each time only model changes not differences in different serializations

  • We could do this locally [there will be so many structural changes a dif won’t work]

• At the moment published versions are in Bitbucket so we need a separate repository to hold published versions in GitHub to replace this

• Jon has started adding files (citation, license, contribution guidance, form for contributions

• One issue about having a missing license file we use cc-by [Note that the Alliance has determined that this is the license to be used by all products. We will need to check license on production programs (cc-by was not on the list of options]

• Document how things move through approval and that people can build on their own branch

• There is a GitHub project called DDI-CDI and DDI-CDI-resources

• Needs to be on DDI Alliance set of repositories

• There is no governance on the Alliance site

ACTION: Jon will start drafting governance documents

Status on CV and pipeline

• We have Simon George booked on 17-18th

• Can we have a repository for DDI-CV-platform (have DDI-CV-publishing)

  • Public
    https://github.com/orgs/ddialliance/repositories?type=all

  • Promo from Postman

Codebook

• Pull request for ddi-c_2
  https://github.com/ddialliance/ddi-c_2
  Note that the first ff3481b is bogus. It is the second commit 0cce353 that contains the documentation changes to codebook.xsd

• How to process through these?

  • People could put in comments in before next meeting for the documentation

  • The documentation content and the next (Concept/ConceptualText) are large. Some review should take place outside of meeting and then deal with questionable areas with group. Future edits should be more localized.

  • Oliver will check to see if there is a clear way to correct and entry error (alt is to reject pull request, kill this Fork and start over)

NEXT WEEK:
Codebook - Documentation review

FUTURE AGENDA ITEMS (as ready):

GitHub administration and guidance

Publication repository on Bitbucket - options/plan

ATTENDEES: Wendy, Jon, Darren, Flavio, Christophe, Jared (guest)
APOLOGIES: Dan

GitHub:

• Darren contacted Jared about AWS account and he needs clarification

• Background:

  • Trying to detach those things that are difficult to do with ICPSR infrastructure (underlying databases for examples, etc.; field level documentation; XML schema; etc.)

  • Set up AWS instances where these can be held

  • example: DDI Lifecycle model generates a lot of output and AWS is a solution

  • Separate web site for documentation and links to sources (docs.ddiaaliance.org)

  • Automation of creation pipeline of CV content from CESSDA output

• Currently we have 5 or 6 administrators already on GitHub - so we can manage rights for individuals

ACTIONS:

• Need to set up an account on AWS so that we can begin organizing this

• Jared needs to set up the account with appropriate permissions

• Darren will ask Michael for the DNS zones

• Wendy and Jon will create a list of items that might move from ICPSR to this new site

Clarification of document repository approach

• CDI will have a place to run their infrastructure

• Outputs will go on AWS

ACTIONS:

• Build a spreadsheet of where things are

• Start a TC ticket and add Darren as a watcher on that

DDI-L 4.0 BETA review of webinar

• Jon has done slides

• In middle of the webinar Jon would like to demo a change on a fork and generate

• 35-40 people are attending

• This is a BETA and there are already errors which need correction

• Public review in summer at the earliest

Questions regarding spreadsheet

• Specific example:

• The blue items on the spreadsheet are only removals

• Some are serialization specific and therefore need to be documented

ACTIONS:

• Add to key meaning of a,e,b in 3.3 column

• Finish sumamry of purpose of moving to Version 4.0 / use of COGS

• Get these posted and link information to Jon so he can add to slides (by Friday)

• What is the current status of CDI - finalizing documentation review checking images, Arofan is wrapping up the documentation and pulling together

XKOS update:

• XKOS best practices document almost finished integration of issues - probably out before COSMOS, maybe next week

• They will create an announcement and we can get this out and posted on the web page

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

Infrastructure:
Set up account - and we need someone to work with Jared
In terms of setting up environment - need someone - Darren is willing to do set up
Getting permissions to the right people
Contact Olof and look for a person to follow-up and manage over time
Apache server serving a static site
Separate containers for different things - keep it simple
cover docs.ddialliance.org instances

AWS issue:
Darren - we can get Simon 2 weeks in March 11-18th) to get the CV set up at UKDA
Moving pipeline off Bitbucket to GitHub: Oliver has already moved it to GitHub and Oliver will send URL of repository
https://github.com/ddialliance/ddi-cv
The creation of repo content is still manual but should be turned into a pipeline in the nexts
Sanda can check out the html specifications. Pascal can also do checks

Webinar
Spreadsheet 3.3 to 4.0 - post for TC and webinar support
Jon has updated the presentation outline based on TC comments
Add Demo of COGS showing how easy it is to make changes and then generate their content for testing
Members planning to attend need to register

FUTURE AGENDA:
Next week: review of webinar in prep
Two weeks: Check in on CV, RDF, and repo pipeline - sanity check

ATTENDEES: Wendy, Dan, Jeremy, Flavio, Oliver
APLOGIES: Jon

DDI-L 4.0 BETA webinar

As of last Friday, we had 35 sign-ups.

Draft of short presentation contents
https://docs.google.com/document/d/1jeqDxr_4P3HM-oeW4j-g-WYr3aAKQeUwNooyilgGWbY/edit?usp=sharing
See document for comments

AWS set up

TC budget for AWS has been approved, so we need to get moving on setting up an account, presumably we need to get Jared to put the Alliance down to pay that.
Uses funding requested this year for infrastructure support. Next fiscal year this should be proposed as a new permanent budget line for association.

Talk to Darren and/or Olof about taking this on to get set up.
Regarding cloud deployment. Whoever sets it up we should management deployment using build scripts. The CV stuff is set up this way and there is something to start with.
We will need to add in things on the documentation. See how long Jared would need to set up the account. Be clear what needs to get done prior to setting up the cloud space and moving things into it.

Product Page

Implications for how the content is made available on the download and doc site for each product
Currently use docflex for the Field level documentation of the XML. Should this be continued with the COGS product. XML specific documentation as well as language specific documentation need for field level documentation.
Can we add to the doc site (links to specific output documentation)

A revised example will be made based on comments. Follow with examples of transfer of all product pages.

ATTENDEES: Wendy, Jon, Dan, Oliver, Christophe
APOLOGIES: Flavio

DDI Lifecycle 4.0 BETA webinar

• Went out on DDI Users Group and some socials

• Put a reminder out 2 weeks before event

• Check with Jared on numbers

• Jon will draft up something for next week

DDI infrastructure proposal

• Has contacted relevant working groups

• CV XKOS and SDTL are fine

• CDI group ok; some longer term issues that can be addressed as they come up in terms of production line

• Add some statement about governance around GitHub

• Can start setting up landing page for development work so we can inform people

Atlassian

• Some worries

• Many people are moving off it and this could cause the loss of open source support (due to lack of paying customers)

• We have moved off in terms of Bitbucket

• But we still have JIRA and Confluence

• Clean up JIRA in the next year to drop unused and archive old issue trackers

• Consider free support services we use to develop contingency plan across the board

NEXT WEEK:

• Product page mockup

• Draft of 4.0 BETA webinar content

• Administrative Data possibility of moving to next fiscal year

ATTENDEES: Wendy, Jon, Dan, Oliver, Flavio

Discuss page change drafts for products (TC-242, TC-243, TC-244)

• Product Page list of versions OK Get this done first as this resolves the Google reference issue

• The page of links for filing issues and how-to page are a good idea

• Product version page revision is a good first step by pushing critical information to the top and making it visible on the initial screen. Continue to revise based on information from developers/implementers and prepare updated draft along with an example from Lifecycle. These need to get updated prior to publication of CDI, new Codebook 2.6, and DDI Lifecycle 4.0.

• Issue to address in future: Current download packages are now served by an on-site (ICPSR) copy of the product and XML is provided for validation purposes through the ICPSR site. How should this change with multiple serializations (XML, RDF, JSON, UML-XMI, etc.)? The Bitbucket repository of published products currently serves as an archive and is not linked to the product pages consistently.

Organization and ongoing management of GitHub content
This was just a heads-up on the type of information TC needs to organize regarding GitHub space. It is primarily management information (Guidelines for development groups and users, tooling pipelines, space management, constraints regarding triggers for moving from free to fee based services, etc.). This is still in a period where we are obtaining comment. These notes from the CDI meeting will be more formally organized and provided in writing by CDI. The Scientific Board is aware of this work and is primarily monitoring the process to ensure input from development groups affected by the shift to GitHub.

TC pages under Learn dropdown on Alliance site
Resources:
We need to look at how examples, tools, and profiles are managed and organized in the new system. We will no longer have the on-site option of underlying databases. Primary decision is which, if any, of these should be managed off-site.
Getting Started:
See TC-245 for collecting information on determining the purpose of this page, what information should be provided, and how to present it. Members were asked to think about these issues and add comments to the issue so that we can move on revising this page in cooperation with the Training Group and probably future Marketing Group. This should be a priority. Jon will talk with Training leaders to get their initial thoughts.

NEXT WEEK:
Webinar for 4.0 Beta

No meeting was held. The following is the information sent out to the group for their attention and action:

TC issue tracker
I have reviewed and updated all entries
In particular see TC-242, TC-243, and TC-244 and add comments regarding layouts provided in attachments

Use filter TC-outstanding to filter out completed issues

Notes from DDI-CDI meeting on 2024-01-17

Comments about Git repository raised during CDI meeting on 2024-01-17 - note that Achim was not present so there will be more
Git repository management - how does TC support product groups in this?
Guidelines
Informational materials
Help identify persons if group is unable to provide this
Deirdre is willing to be involved as setting this up
Back-up people
Git repository
Tools/workflows

Organizing BETA access, support repository, policy, pull requests
Coordinate how to organize
Working with input from outside of the group (developers work)
Making clear what things are
Granularity of pull requests (issue based)
Branching - readme on how to do this, what is supported
Pricing models for AWS (space is not the issue, but deploying own servers/code base)

Each product needs to provide a canonical expression of the product
CDI is the UML model expressed as canonical XMI
Each product needs to be clear on this - how to visualize the model in the case of COGS base
Canonical model has to be publicly distributed

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

Update on CDI work

• Variable Cascade issues - providing guidance through webinars, documentation (it appeared there weren't direct predicates linking along the chain, appeared there were just a single predicate used for different relationships)

• Will this require additional review?

Topics for future webinars

• Why are there various ways in dealing with the same content across products (classification/codelists etc)

DDI-L 4.0 BETA review

• Supplemental content - changes in the content model; why and what was done; update DDI Lifecycle Best Practices (how to use some of the schema structures to address 4.0 in addition to 3.x best practices)

• Updating model - just raising issues and modifying at the end

EDDI session on priorities

• Nothing specific struck a cord in terms of TC

Follow-up on - web pages and webinar with Jared

• Wendy has recieved comments on pages

• Jared has responded to Jon who will make arrangements for webinar on 4.0 BETA

ATTENDEES: Wendy, Jon, Dan, Jeremy, Flavio

DDI-Lifecycle version 4.0 beta follow-up

Webinar of some description
Q&A - Highlight of why we moved to this and how they can interract with it
or Anticipation - presentation

• Q&A seems best approach

• A bit of introduction to version 4.0 (about 5 minutes)

• Back end of February would be good timing

• Discussion pieces out from mid-Jan to mid-Feb: get a list together and see what is important to front-end

• 3:00 UK (10 eastern, 9 central) - 21st or 28th of Feb (Jon will follow-up on this)

• It's about a small group zoom with google form for registration

• We've only really asked about OWL serializations

• Do we want something more on the model conceptualization?

• On the serialization things?

• Model is the same as 3.3 with only changes made to so only specific changes for choice and physical description

ACTIVITY: (Wendy review and create list) pull discussion pieces together, clean up, post, and send links
Roll out discussion pieces.

Product pages on Alliance Site

Overview of products page can be updated but is in good shape overall
https://ddialliance.org/products/overview-of-current-products
Product pages:

• Less wordy

• More prominence for the access to the html documentation

• Update links

• Setting up pages that were held off the site (determine what should be off site support - RDF resolution

• All of the products have autogenerated documentation - move to a docs.documentation site and link from the main pages

• Examples, tools, etc are candidates for moving off-site

• Get comments from Jared (contact him for what feedback he's gotten)