-
Notifications
You must be signed in to change notification settings - Fork 71
March 7, 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
- Daniel Lamb
- Mark Jordan
- Rosie LeFaive
- Jared Whiklo 🥁
- Seth Shaw
- Bryan Brown
- Diego Pino
- Andrija
- Marcus Barnes
- Kim Pham
- Natkeeran Kanthan
-
Currently there is a clear separation between Drupal (content management) and Fedora (preservation). It addresses concerns relating to preservation. In the current architecture, Drupal is be primacy. How do we support the following use cases:
- Same fedora repository with isolated (namespaced) content, multiple front ends (Drupal multi sites connecting to same fedora/triplestore backend?)
- Same fedora repository with some shared content, multiple front ends
- Related Issues
-
Handling of authorities data
- For IRs: need to be able to create/edit data for faculty/students
- What to do about journals/conferences/departments that may already have URLs, but not URIs?
- Linked data UX for content submitters
- How to make it easy for users to enter data that gets stored as a URI on the backend?
- Local data: authority content types?
- Existing data: something like Solr autocomplete?
- For IRs: need to be able to create/edit data for faculty/students
-
... (feel free to add agenda items)
-
Multi-site discussions from last week. In the current release all the content is in Fedora and you can namespace. There is one use-case where the same content gets used in two drupal sites.
Danny - It is tricky once you break that separation. You could make a third section and that is the "shared" space between site A and B.
Nat - Drupal doesn't share content right now. Currently we are creating a container and change the configurations to point to the container. So each Drupal site can access a different container in Fedora as the holder. It could be made configurable.
Danny - You could add as part of the message an attachment whatever information you need to share.
Rosie - In CLAW do we have the idea of a root container.
Danny - It is sort of implicitly defined as the root of the Fedora container. But there is nothing stopping you from adjusting that.
Bryan - What about https://www.drupal.org/project/domain, is alpha but seems to have a way to allow some restrictions based on how you come into the site.
Andrija - https://github.com/agentrickard/domain for the module code.
Danny - Wanting to put different things into different namespace would fit into the context, perhaps we can do that in there. At the very least to share that with all the downstream services. Configuration should be in Drupal.
-
Authorities - Local? Remote? Hybrid? HolaToast? <drum fill>
Danny - I don't think we will avoid a situation where we will have both, we may want to use a remote URI but we want to use sort of like a Solr auto-complete for authority.
Bryan - This is a separation between archives versus institutional repositories. IRs are the situation where you will have to be minting a bunch of new URIs for local students/researchers.
Its really hard to get stuff in LoC, so ideally if you have a student or faculty you will probably have to mint a local URI.
Seth - We will create a node for each local authority and put all the information we want into there. Then sync external data on a periodic basis.
Danny - You are looking to update the Drupal fields or are you hacking Solr.
Seth - We would store them in Drupal.
Mark - Isn't that what the triplestore is meant for?
Danny - There is no functionality that requires the triplestore.
Mark - Make Solr as cache for authority searches.
Bryan - Even if a person has an ORCID then we will still need to populate more data for most of our users. Then also add SKOS or OWL relationships to those external URIs.
Jared - For archivists do we want to store all the data locally or just pull it in and apply the changes.
Seth - For archivespace there is a space for a page of this is not local, pull it in from somewhere, then apply it locally.
Bryan - What do we call this as the Entities Solution Pack seemed to be a problem.
Seth - I was going to make a content type for Person, Corporation, Subject.
Danny - Are you talking about tagging something as external
Seth - No you would incorporate an external external taxonomy and then incorporate it.
Rosie - Which is fine until you want to load the entire MeSH headings to use one or more.
Rosie - URI reuse within the repository is important even if it is Dogs in Wheelbarrows from the LoC.
... lots more discussion ...
Consensus is bringing external data into and adding new, the way of doing this is still TBD.
MOAR USE CASES!
-
Is it possible to index things that are custom Drupal entities?
Danny - Oh yeah, we definitely don't want to limit people from being able to index as long as it has a mapping and the JSON serializer understands it.
-
How are we going to separate out the viewer functionality for things that might not have simple off the shelf Drupal viewer functionality?
Danny - Yeah and we are going to be on the hook for various types. We are going to try to stick as close to core Drupal as possible and with display modes we can switch out.
-
Drupal 8.5 is landing... what do we need to be aware of? Because we are not pinning things down in claw-playbook you will start seeing it tomorrow.
But we probably should be locking it down via some pointing to our fork of drupal-project to slow our adoption of the bleed-edge at some point.
You may be looking for the islandora-community wiki · new to islandora? · community calendar · interest groups · roadmap