-
Notifications
You must be signed in to change notification settings - Fork 71
March 4, 2020
Debbie Flitner edited this page Mar 4, 2020
·
11 revisions
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/203396828
- Join us on the Slack Islandora 8 Channel https://islandora.slack.com/archives/CM5PPAV28
- Danny Lamb
- Danny Bernstein
- Melissa Anez
- Mark Jordan
- Don Richards
- Eli Zoller
- Alan Stanley
- Bethany Seeger
- Debbie Flitner 🌠
- Tammy Wolf
- Alexander O'Neill
- Noella MacIntyre
- Cary Gordon
- Willow Gillingham
- Jared Whiklo
- Aaron Birkland
- Centralized logging of derivative creation
- Documentation on preservation strategies using Islandora
- Draft docs started at https://github.com/mjordan/digital_preservation_using_islandora
- Dealing with conflicts between filesystem schema as defined in field definitions and derivative actions.
- Versioning of media and files
- Optionally appending fedora namespaces when interacting with Gemini and Milliner (dbernstein)
- Release Milestone Issues
-
Centralized logging of derivative creation
- What is the best way to approach centralized logging of success/failure? So people can track problems during batch ingests, etc.
- Should be some dashboard/visual feedback that derivative creation was done. Might be useful to create an event entity that requests and action and has expected results - comparison of expected and actual results. Since Drupal is getting the derivatives we can use that rather than having each service report what it’s doing. Purge old logs periodically.
- Watchdog might not be the best spot but could make a separate list. There are tools for log aggregating, many are proprietary, not sure what else is available.
- Spitball - event just calls for derivatives, could we add event that reports the action was done. Or something. Worried about infinitely growing logs in the database. Helpful to see when things started going wrong.
- System stability info vs preservation continuity. Amount of time maybe could be configurable with info about what the settings mean. Up to admin if they want to keep loads of info for preservation purposes.
- Good use case and we should work on it for next release. Manager view on an item that shows fixity checks and derivative logs, etc.
- Related issue: Report background job success/failure
-
Documentation on preservation strategies using Islandora
-
Draft docs started at https://github.com/mjordan/digital_preservation_using_islandora
-
Deferring to a later call. Please see docs and feel free to work on them.
-
-
Dealing with conflicts between filesystem schema as defined in field definitions and derivative actions.
- When setting up fields on media types you set where you want the media stored (can set file folder). Also can set filesystem in derivative actions. There can be a conflict.
- Alan has written a modification so filesystem is only set in one place. Seth likes being able to split due to some custom derivatives that they send to Fedora.
- Alan will submit the code for review. No real consensus on what is preferred, both options are desired. Perhaps better documentation and maybe a warning while creating the settings.
-
Versioning of media and files
- Eli has put in a couple of PRs for versioning of media - one isn’t passing tests so need to check it. Media going through Milliner might be forcing a 1-to-1 relationship - that 1 media has 1 file.
- File replace module - Drupal normally won’t let you write over an existing file. Module creates a UI endpoint that lets you replace the file (admin/content/files/replace/[fid]). Modified flysystem adapter for Fedora to create a version if the thing already exists but this would depend on the File replace module and using it to replace the file instead of just changing the original file.
- Maybe need to update form and replace file widget with a widget that uses this module directly or add a message to send them to the replace URL for updates.
-
Optionally appending fedora namespaces when interacting with Gemini and Milliner (dbernstein)
- Crayfish services seem to have 1-to-1 relationship with Fedora resource (sort of a root path for Fedora). They don’t get it from Islandora or messages from Fedora. So how can we ensure the mappings in Gemini get namespace prefixed.
- Can see Fedora URL in Islandora settings. Can’t change it but it only shows what it pulls from settings.php.
- Resources created in Fedora don’t have the namespace. Islandora is sending out the message to create Fedora resource and then Milliner/Gemini converts it but only uses the Fedora base URI and doesn’t get the namespace.
- Nat had a fix to send whole host URL but maybe not merged or didn't do it from Fedora side.
- Things that are configuration for a microservice need to be exposed in Drupal settings rather than set directly in the microservice settings.
- This should be in. Config to point to multiple Fedoras and they wrote to separate trees.
- Everyone tries to figure out what Danny B needs to do/change to get this to work. Debug options to see if correct versions are being used, check Alpaca/Karaf messages being sent and what info is going along with them.
- https://github.com/Islandora/islandora/blob/8.x-1.x/src/EventGenerator/EmitEvent.php#L134
-
- tl;dr Dependency hell. Now fixed.
- Success with >2GB files but running into errors with large videos.
- Running out of time, need additional info/testing on beefier environments.
-
Openseadragon and paged content on remote installs
- Possibly a duplicate of this
- Ran out of time
You may be looking for the islandora-community wiki · new to islandora? · community calendar · interest groups · roadmap