CLAW Migration Sprint Wrap Up Meeting

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join. Here is the info:

• Time: 12:00pm Eastern Daylight Time US (UTC-4)
• Zoom link: https://zoom.us/j/203396828
• IRC:
  • Join the #islandora chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #islandora on irc.freenode.net

Attendees

Agenda

• Issues
  • https://github.com/Islandora-CLAW/CLAW/issues/908
  • https://github.com/Islandora-CLAW/CLAW/issues/905
  • https://github.com/Islandora-CLAW/CLAW/issues/902
  • https://github.com/Islandora-CLAW/CLAW/issues/901
  • https://github.com/Islandora-CLAW/CLAW/issues/912
  • https://github.com/Islandora-CLAW/CLAW/issues/913
  • https://github.com/Islandora-CLAW/CLAW/issues/914
  • https://github.com/Islandora-CLAW/CLAW/issues/915
• OpenRefine Thoughts?
• Roundtable

Minutes

1. Issues
   1. PR is in, needs testing
   2. Andrija and Danny have had some communication, still working on the Drupal migration. Also there is alot of work in migrating xml to csv before using
   3. PR needs a rebase. To test this Jared needs to run this in a clean environment.
   4. Blocked until #902 comes in. The tests would be to create an entity with a controlled_access_term field with X term and Y linked field.
   5. Controlled access terms as taxonomies. Seth has a branch which could subsume #902
   6. Investigating xml2csv and how we can use this for the larger community. Might be easier to re-export the data as MODS because you can then use XPaths and avoid issues around different XML attributes. Also need to store multi-values some way (ie. Role terms with the Agent). If we can get all these out to ensure that OpenRefine will do the work it needs to do.
   7. Documentation around getting these multi-value fields to separate columns for use in OpenRefine.
2. OpenRefine discussion.
   • The MODS export from OpenRefine, it has its own templating language. Mark Jordan has created a twig template for creating MODS out of a csv spreadsheet.
   • Taxonomies for types are currently broken into a taxonomy for MARC types, one for DC types. Would it be acceptable to have a single field to pull from either field. Pretty sure that the predicate chosen would allow types from either MARC or DCTerms.
   • Multiple values allowed in typeOfResource field? Yes.
   • Do the MARC and DCTerms need to be in separate vocabularies or can they be in the same one? It could be confusing to a user to have "Image" and "Image" available, so you might have to prefix them. Perhaps we can use a view as the autocomplete and also display the external URI so that an end-user can see the difference between 2 terms that share the same name but have different URIs.
3. Translated titles can cause the need of having another migration, but there are issues raised here https://docs.google.com/document/d/1PyQLTbEyQjaZ_FO4w04gg2MWdV_uERtozEYl1X3YJwQ