November 13, 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

1. Daniel Lamb
2. Melissa Anez
3. Alexander O'Neill
4. Chris Kellen
5. Debbie Flitner 🌠
6. Don Richards
7. Jared Whiklo
8. Mark Jordan
9. Natkeeran
10. Noella MacIntyre
11. Rosie Le Faive
12. Seth Shaw
13. Cary Gordon

Agenda

1. Documentation Sprint Progress
2. Can we close the meta-issue on versioning?
3. FITS is still out there: https://github.com/Islandora-Devops/islandora-playbook/pull/129
4. Upload Form Demo
5. Issue Roundup:
   1. Filemime constant mapping
   2. Auto-publish docs?
   3. Openseadragon view mode sets the viewer to a small fixed width
   4. Islandora.tomcat8 Ansible role has deprecated 'sudo:' directives
6. ... (feel free to add agenda items)

Minutes

1. Document sprint progress:

   • Sprint kickoff yesterday. There is now a document with info about the sprint as well as a spreadsheet for signups and progress.
   • Per Melissa’s recommendation, Danny has re-opened issue #1040 for the doc sprint.

2. Versioning meta-issue:

   • We have been keeping these kinds of issues open to help track related issues, should we close them or should they live forever to continue to track?
   • Q: has it been clearly documenting how we’re doing versioning? This might determine whether to close.
   • Q: Is there a way to view versions? A: just nodes.
   • Versioning is live/working but there are some quirks. Versioning binaries (i.e. files) doesn’t quite work due to the way forms work. Let’s get documentation in there before closing.
   • If you create a media with a file, that’s fine. Updating metadata creates new version, fine. But deleting the file in file field and uploading a new one creates a new binary resource with _0 on end of filename. This is the documented way to update the file but doesn’t exactly replace it.
   • We are subverting some of the code to get it to work the way we want. Drupal doesn’t want to let you update files via PUT.
   • Maybe let this be a documented issue and put in the roadmap to fix in a future release.
   • Could also delete the media with the file to get a new one. Can version all other resources/nodes that are non-binary/not files.

   Decision: Hold off on closing until everything is done and documented.

3. FITS PR still out there. Still works just fine. Please check it out and test so we can merge it.

4. Upload Form Demo: TL;DR: The demo shows a great feature but opened a can of worms regarding what is an Islandora Object and what are we doing anyway?

   1. Danny shows the demo:
   • Hijacked add media and add children buttons to point to this new form. Still need to figure out how to handle paged content.
   • Add media goes straight to add file button and usage checkboxes.
   • Add children just goes straight to add (multiple) file field, easy removal of added files.
   • Can be different types of files. Submit.
   • Upload limits are still governed by php.ini file.
   • Processes media, creates viewer/media based on mime type.
   • Had to change contexts to tag viewers based on mime type.
   • Firing off all of these requests all at once like this is a good test of Camel. Will eventually get through all the derivatives, etc but may take time depending on box resources.
   • Cuts down on a lot of clicking for adding lots of items.
   • Has config to do some settings, upload URL pattern, content type to make, what mime types to allow.
   2. Discussion of demo:
   • Lots of cool stuff to do with it, we should define some of them. Make some use cases, etc.
   • Need options for pulling in metadata for items.
   • It makes some assumptions about how we interact with our objects and perhaps we need to rethink our assumptions.
   • Are there use cases where we need to do things differently? Eg multi-page items can have page number, weight by upload order, etc.
   • Maybe form field for token pattern.
   • Could add templating fields/tokens to settings form based on content type user has selected to populate metadata for the items created.
   • Suggestion: checkbox on upload form to template uploads for multi-page items.
   • May need further discussion on content modeling, what is an islandora object, do we have a file or a concept of a thing represented by a file/multiple files.
   • Example: Data set is a set of stuff - one object represented by 12 spreadsheets.
   • Big picture question: maybe get guidance by looking at how we would have done this in 7.x.
   • Need conversation about what islandora needs to do. This upload form solves one problem but is it something that it should be doing all the time?
   • Islandora is so modular that you can do anything but there is no conceptual model that ties it all together. Discussion about “what is your islandora object?”.
   • Develop skeletons to meet these needs rather than trying to have one thing that does everything.
   • Concern raised about PCDM. Docs refer to PCDM and we use some of the vocabulary but we don’t require PCDM or say it anywhere though we are doing it by default.

   Danny wanted to make the upload form as small as possible. Reduce clicks and make a better user experience. It definitely also kicked off a giant discussion.

5. Issue roundup:

   1. Skipped.
   2. Auto-publish docs #1327: Danny will do this as part of doc sprint.
   3. Openseadragon viewer has constrained width #1328. Danny found this as part of his upload form change. Needs verification. Maybe related to Carapace update. Reacts to parent container width, maybe related to login box.
   4. Ran out of time.

Action items

Next week, come with topics we want to discuss in a larger community meeting about what to expect from Islandora.