...
2022-2023 Minutes Page, 2020-2021 Minutes Page, 2018-2019 Minutes Page, 2016-2017 Minutes Page, Pre-2016 Minutes Page
Expand |
---|
|
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) |
Expand |
---|
|
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: 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 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 Jira Legacy |
---|
server | System Jira |
---|
serverId | b62a0bb6-d990-3186-ba9e-0c3828bdee04 |
---|
key | DDICODE-95 |
---|
| deprecation - URI attributes needed DDICODE-97 move license element to useStmt |
...