July 22, 2020

Time/Place

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

Time: 1:00pm Eastern Standard Time US (UTC-5)
Zoom link: https://zoom.us/j/97345581392
Join us on the Slack Islandora 8 Channel https://islandora.slack.com/archives/CM5PPAV28

largely gremlin free
breakout room worked out well
outcome: need more documentation - how do know what we are lacking in terms of documentation or is it an issue of people can't find them? or both?
- suggestion: use use cases to help fill gaps in documentations
- issues from drupal site administrators not knowing how to use drupal/islandora - like a getting started beyond the installataion process (OJS is a model to look at)
- more examples for migrating different types of files from d7 -> d8
- writing documentation is hard and its difficult without paid staff dedicated to that work
- as community matures, we need more in-depth niche documentation
- can be helpful to pointing to drupal docs as much as possible
lots of metadata stuff came up - considering recommending for D7 migration - migrating datastreams to D8 and then working in D8 to pull the metadata out of the datastream and into Drupal fields
the stack has matured to the point where its much faster and easier to get a stack setup so what communities did we miss because it was so hard to get started. now we should have more players at the table, more use cases, etc.
should we add more people to the committers so that more people can merge in documentation PRs?

ISLE work is wrapping up. It will assuredly replace the ansible setup.
It'd be best if the tickets in Islandora-devops/isle-dc is moved to islandora/documentation.
LSAP processed already completed - the project started in islandora-devops

Issue Roundup a. https://github.com/Islandora/documentation/issues/1564 - flysystem provides a function to override the file. drupal doesn't let you recreate a file with the same name (we think this is a limitation of the widget and the garbage collector doesn't clean up well). in theory the flysystem implementation is handling the replacing of files for all of the plugins but its worth checking into that - s3 was given as an example. seth mentioned we had previously discussed writing our own widget for uploading to fix some of these, but we haven't done that yet. two separate cases in the ticket: actually truly deleting or replacing the file (which would be versioning). the current widget doesn't allow you to specify the filesystem, so that's something we could consider adding in a custom widget (its currently handled in other places in the configuration) - but we'd have to allow that to be configurable. there is concern of telling where media live - we'd probably need to have a custom dashboard (view) to spell that out.

suggested to have separate non-technical user-focused meetings to tease out changes and feature requests - will be taken to ICC for discussion

This is an archive. For new Tech Call notes, click here