October 30, 2019

Time/Place

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

• Time: 1: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

• Danny Lamb
• Melissa Anez
• Alan Stanley
• Alexander O'Neill
• Daniel Aitken
• Don Richards
• Eli Zoller 🌠
• Jared Whiklo
• Noella MacIntyre
• Rosie Le Faive
• Seth Shaw
• Yamil Suarez
• Bethany Seeger
• Willow Gillingham

Agenda

🎃 🎃 🎃

1. Documentation Sprint - November 11th - 22nd
   1. Sign Up Sheet
   2. Pick a page
2. Islandora/Fedora Camp next February
3. CLAWdit is nearly done. Spreadsheet
4. Issue Roundup
   1. Slack Notifications 👿
   2. What's up with the Islandora 8 RDF namespace?
   3. Documentation: Bad link to docs in repo homepage
   4. --userid option for migrations doesn't work on rollback
   5. migrate 7.x settings
5. ... (feel free to add agenda items)

Minutes

1. Documentation Sprint - November 11th - 22nd
   1. Sign Up! Claim a page or be a buddy
2. Islandora/Fedora Camp next February, Feb 24-26
   1. focus on Islandora 8, so preference will be given to that
3. CLAWdit is nearly done.
   1. carapace pull remaining, already approved by @manez, just needs a committee to approve. thanks @dflitner!
   2. documentation repo cleanup will happen in the documentation sprint
4. Issue Roundup
   1. Slack Notifications - basically not working except if you put the token right into the .travis.yml. major issue is that we have unknown people submitting PRs which doesn't allow encryption. possibly need a ticket to travis. will rely on the github integration telling us of travis failures. will be put into the #notifications channel
   2. What's up with the Islandora 8 RDF namespace? - was introduced as a matter of placeholder convenience during development. we should probably document this. used to be the clawntology but that seems to have disappeared, may need to be added to the islandora_ontology repo. We should be consistent and correct. what's the best practice for versioning ontologies - we'll need a v1 for the islandora 7, a v2 for islandora 8+. look into what is best practice for versioning ontologies - mark jordan volunteered to do this.
   3. Documentation: Bad link to docs in repo homepage - a PR was put in but already resolved in another PR.
   4. --userid option for migrations doesn't work on rollback - --userid option is not available for rollbacks. this is added by islandora because of the need for the JWT token (to validate permissions). seth put in a PR, check it out and try it.
   5. migrate 7.x settings - add a UI for the islandora 7 parameters for migration. may be a little difficult to get it to update multiple yaml files. would be a nice improvement! you could probably use a twig template. alan has done something in riprap. danny suggests looking at entity import (a UI for drupal 8 migrations).
5. Other Topics
   1. TUS(https://tus.io/) - checks to see if the file is already in the system, so if you use the same file twice, it doesn't upload it twice. this is the way drupal thinks to use media also. this is good for getting things in but not good if you try to delete one, would need to put a filter on or something that would say don't delete something that is still a member of something else. in islandora, you currently can't have a file be a member of two objects. but there is nothing actually preventing people from changing that in the config, maybe we should explicitly prevent that. you can disallow duplicate files in the file hash modules, but this is currently not enabled. alan reports so far TUS is working better than plupload. easy solution would be to blow away the TUS cache but its a shared cache so you'd have to target a particular file since multiple people can upload at the same time. No one seemed to be using sharing files among media but people want to be able to use media among multiple nodes (ie. an exhibit scenario - should probably use an exhibit node connecting to media to preserve the relationship of media connected to nodes data model). TL;DR from danny: conclusion was it works but there's implications if people want to share media amongst