-
Notifications
You must be signed in to change notification settings - Fork 71
January 10, 2018
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)
- Dial-in Number: (641) 715-3570
- Participant Code: 304589#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
- 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
- Kim Pham
- Jared Whiklo
- Danny Lamb
- Natkeeran 🌟
- Rosie LeFaive
- Mark Jordan
- Seth Shaw
- https://github.com/Islandora-CLAW/islandora/pull/68 has landed
- Related Link Headers: https://github.com/Islandora-CLAW/islandora/pull/71
-
https://github.com/Islandora-Devops/claw-playbook/pull/43 is pending. What else should go in first?
- Currently testing a re-work of https://github.com/Islandora-Devops/claw-playbook/pull/22 that will affect multiple roles
- https://github.com/Islandora-Devops/claw-playbook/pull/44 needs testing too, but won't affect #43.
- Multisite architecture - how should we setup multisites in CLAW? Use Fedora hierarchy? Using separate namespaces in triplestores? Any updates from https://github.com/Islandora-CLAW/CLAW/issues/396
- ... (feel free to add agenda items)
Danny - We are using context rather than rules. Context provides custom actions, reactions and conditions. Can be configured via UI. This is a major change. We can break out of the 1-bundle-1-content type limitation.
Danny - Link Header related PRs sit on top of the context work. Link headers have been via even subscribers. Link Headers can be used to navigate the repository. Link Headers obey the authorization controls. With these Link Header information, we have sufficient information to generate derivatives.
Danny - With regards to using external roles, I though we might have to bring in changes. But, Jared has done much of the work in bringing in the changes.
Seth - Working on patches/changes related to CentOS support.
Danny - If variables need to be used in multiple roles, it should go into group vars.
Seth - Once the PRs related to external roles is merged, I will be issues PRs related to CentOS support and vars.
Danny - For fedora, top level roots can be used separate separate sites/projects.
Jared - You can also use separate Fedora.
Danny - For triplestore, yes, you use different namespaces. Named graphs may also be an option.
Kim - Currently we have all in one server. We are planning to move the Drupal/web server into the production server. We are wondering how to separate and support
Jared - Should Fedora objects have all the relationship links themselves. Currently, we need to go through Drupal to establish the relationships. Should we have a micro service to handle this.
Danny - The question is should the Fedora be just a back of Drupal information. Or should it be a repository with all the information.
Mark Jordan - Would this service add any overhead and cause any scale-ability issues?
Jared - One possibility is to convert Gemini as public facing service and do the translation as needed.
Rosie - Does Fedora or Drupal populate the triplestore?
Jared - It may be possible add the info as triples and query that information.
Jared - I would like to be able to traverse the Fedora repository separately. If we want to have the Fedora publicly available, then this is needed.
Rosie - I am for using Fedora to the full extent.
Mark Jordan - In Fedora 3.x, the UI was useful for analysis and troubleshooting. Would be useful to traverse/map the repository.
Jared - This feature is needed to traverse the objects within Fedora. It would not give visualisation/context out of the box.
Seth - One of the original goals was to sync back to Drupal. If Fedora does not have this information, it would be difficult to accomplish this.
Rosie - Currently, the relationship info is in Drupal. Currently this is mirrored in Fedora, but they are pointing back to Drupal. The suggestion is to have the corresponding
Mark Jordan - It is not necessarily exact graphs. Subset of information would be in Fedora.
Jared - Should all information in both places: Drupal and Fedora. Yes, the graphs would be same (for now) in content, but the identifiers would be different.
Rosie - It is the Gemini that translates the identifiers.
Jared - Gemini is an important component piece of the stack. We have ensure its persistence.
Rosie - Drupal id is the id of display version. Fedora is the id of the preservation version.
Jared - Yes, they are two graphs. And combination of two graphs will give you the complete info about the object.
Danny - We don't want to release and have people come back with issues related to mirroring the repository.
Danny - We may have to come up with a way to store the preservation copy in Fedora, then have a marker for that in Drupal.
Seth - Should we create use cases to follow up with this issue.
You may be looking for the islandora-community wiki · new to islandora? · community calendar · interest groups · roadmap