Versions Compared

Old Version 114

changes.mady.by.user Wendy Thomas

Saved on

compared with

New Version 115

changes.mady.by.user Wendy Thomas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

2022-2023 Minutes Page, 2020-2021 Minutes Page, 2018-2019 Minutes Page, 2016-2017 Minutes Page, Pre-2016 Minutes Page

Expand
title2024-05-23

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

Expand
title2024-05-16

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)

...