...
2022-2023 Minutes Page, 2020-2021 Minutes Page, 2018-2019 Minutes Page, 2016-2017 Minutes Page, Pre-2016 Minutes Page
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Jon, Darren, Flavio Quick recap
Next steps
Summary
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jeremy, Dan Quick recap
Next steps
Summary
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: 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 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 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. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Darren, Dan, Jeremy, Flavio Quick recap
Next steps
Summary
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. |
Expand | ||
---|---|---|
| ||
CDI pre-vote webinar |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Jon, Dan, Jeremy AGENDA: Quick recap Next steps
Summary 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 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 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: 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. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Jeremy, Dan, Darren, Flavio Quick recapWendy 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
SummaryCDI Status Update and Issue ResolutionWendy 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 AutomationWendy, 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 TrackerWendy 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 AnnouncementWendy 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 RolesWendy 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 DiscussionWendy 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 PlanningWendy 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 TableWendy 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 TasksWendy 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. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Darren, Dan, Flavio, Jeremy AGENDA:
Quick recapThe 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
SummaryDDI 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.
Website Management Agreement DiscussionWendy 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.
Transition Timeline and Checklist DiscussionWendy 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.
FUTURE MEETINGS: |
...
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Jeremy, Dan XKOS: redirect to: CDI example of HTML redirect Quick recapThe 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
SummaryResumed 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. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Darren, Jeremy, Dan Roadmap/timeline requirement CDI timeline CV update Sanda wants to do more changes on the home page. Should be live next week. Entry shifts from Jared to Darren HubSpot update Oliver - website transition
Product section
Presentation proposal for EDDI on Roadmap
ZOOM SUMMARY (edited)Meeting summary for Technical Committee (08/22/2024) Quick recapThe 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. SummaryPayment Processing and Roadmap Discussion Project Timelines and Database Import 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 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 CDI Project Progress and Roadmap |
...
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Dan, Jeremy, Darren, Jared (guest) F2F and Web site planning See https://docs.google.com/document/d/1DIPnvDMWo6SNxxf7bH4O5cwWCUWkrHL-aDlRNCqVM9M/edit?usp=sharing ACTIONS:
Wendy: (Notification to Content Managers)
Text of email: 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:
Thank you for your help with this move, Use of Zoom Summary Post meeting:
ZOOM SUMMARY (edited)Meeting summary for Technical Committee (08/08/2024) Quick recap
Next steps
Summary
Website Changes and Emus Discussion University Website Security Incident Discussion Addressing HTML Repetition in RDF Release News Item URL Structure Discussion Improving Member List and Publication Functions Organizing Documents on New Website Improving Working Group Organization and Communication Database Dump and Site Updates Strategy Transportation, Arrivals, and Notifications |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Jeremy, Oliver, Flavio Codebook - Pull Request 41 F2F 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 CDIF 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
Next steps
SummaryAddressing Code Book Issues and Feedback Website Hosting Change and Challenges Site Transfer and Backup Plan Discussion Addressing Duplicate Language Labels Addressing Content Management System Issues Addressing CV Groups Language Label Issue docs.alliance.org Website Structure Upcoming Developments and Transparency Concerns |
...