TC Meeting Minutes

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.

• DC Tabular Application Profiles (DC TAP) - 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
GitHub - ddialliance/docs.ddialliance.org: Static content for docs.ddialliance.org website

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