Date and Time

March 9, 2017, 2pm EDT

Connection Information

Moderator: scossu

Notetaker: scossu

Notetaker?
Review last week's action items
Review code progress
Further discussion on wireframes?
Discuss public facing name for FileSets
1. Should convey difference between Files and FileSets
2. Should be easy to understand and memorize by non-technical users
Next steps

Prev. action items:
1. PCDM validator needs some additional work before submitting to the community
2. Also some additional info gathering needed for file association questions
3. targeting next week to complete this
4. This can be pitched for Dev congress + LDCX
Work on validator code
1. yml file decoupled from QA but it will be possible for individual implementers to plug QA in
2. Expose ability to set custom validation config file
3. Other uses outside of pcdmuse: namespace are possible
4. This file is currently focusing on validation config; UI config can be tackled later and likely in a separate place
5. This is basically a generic RDF type validator; we could use some existing AF machinery
  1. With the addition that we need to check that a file associated with a given use (RDF) type exist
6. Whenever you change your type, AF will need to be able to tell the types that should not be removed
Wireframes
1. Create page: Adam Wead already implemented this in LAKEshore; should be possible to extrapolate the code from LAKEshore and put in Hyrax
  1. We can do all validation in the UI via AJAX and display error messages if validation fails at an point
  2. Have a separate service to handle validation logic
2. Ran out of time to comment on other pages; no particular red flag at a quick glance
Engaging other developers
1. Complete validation PR
2. Define a clear path and present to dev congress

Andrew Myers Complete validation PR
Andrew Myers post file to file associations question to the tech list
Adam Wead summarise the rdf:type issue to the tech list; what problems would the solution cause