List is in table, assigning issues (tagged with “Feedback”) to separate repositories
and also a link to the selected issues for M4 is there
Alex organizes the issues also by SP feedback, but discussions should go on in single items issues, so that we can keep track
issue #66 discussed and change proposed
issue #94 was commented by Wolfgang, Alex will add this to the profile list of issues, @Wolfgang Zenk-Möltgen will inform @Darren Bell
Profile feedback and DDI 3.2 Profile work
issues in cessda.metadata.profiles will be discussed in the group (but Darren needs to do an update)
Taina offers to go throu those issues and assign them to CDC or CMM or CMV (together with Katja and Wolfgang, maybe Esra) during next week (finalized until Nov 18th) @Wolfgang Zenk-Möltgen creates a doodle.
Responding to feedback: Alex has already sent email responses with general information. @alexander-muehlbauer will also send an email over basecamp to everybody, informing about the issue with the overview
AOB
Question by Taina: Can CMV use the SKOSMOS style API (used by CVS in the future)? Alex will look into that. New features may be a reason for that. CMV currently needs the CVS API: @alexander-muehlbauer and @alexander-muehlbauer will talk to Claus-Peter Klas about CVS.
cessda-bitbucket-importer
commented
3 years ago
Original report on BitBucket by Wolfgang Zenk-Möltgen.
Participants
Agenda
Close Meeting notes 2020-10-28 #91
Summary of CMV feedback and M4 issues
Profile feedback and DDI 3.2 Profile work
Responding to feedback: Alex has already sent email responses with general information. @alexander-muehlbauer will also send an email over basecamp to everybody, informing about the issue with the overview
AOB