April 11, 2018

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)
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

Attendees

Agenda

Content Modeling Rodeo
1. Taxonomies for Content Model and "Media Model" (e.g. DSIDs)
  1. Taxonomy terms can have fields, so an 'external uri' field is super easy to implement.
  2. Use a single bundle as metadata profile, tag with content model to drive behaviour
    1. Field Group module can get us pretty close to something that looks like a form builder form.
  3. If you need a different metadata profile, make another bundle! Nothing bundle specific at this point, it's all about tagging with taxonomies
  4. Use Permissions By Term module to associate roles with tags.
  5. Already have PR in to swap view and form modes using Context (which can easily be controlled via tags)
  6. Needs Structure Sync to guarantee consistency when installing / pushing to prod.
2. Using core media module gives us audio and video entities with basic displays in addition to images and generic files.
3. Reverse media relationships
  1. "Media Of" field analagous to "Member Of" (could even the same field, really)
  2. Use views to generate a "manage" page for media
  3. Action link to add media to node (use Prepopulate module to pre-fill form)
  4. Use EVA module to still display media through object display modes
Open questions left
1. Ordering of child nodes / hierarchies (e.g. books and newspapers)
  1. Core book module - works, gives breadcrumbs and prev/next navigation with a hierarchy, but totally brutal UX
  2. Just use taxonomies? tempting, but feels wrong
  3. Entity Reference Hierarchy module - Basically adds a weight in addition to a parent reference. You get breadcrumbs for free, but admin page for children only works on immediate children (so hierarchy manipulation is a bit disconnected).
  4. Entity Queue - Creates orderings as config entities. Great views integration (you can use a queue as a sort in a view), used a lot, but still a bit clunky.
  5. Draggable Views - I see what it's trying to do, but it's buggy as all get out
  6. Weight - hijacks sticky field to use as a weight... pretty hacky
2. Translating terms to RDF. What's better, a "hasContentModel" predicate with taxonomy terms, or using the taxonomy to enhance rdf:type?
3. What to call entities for people/organizations? (I've been improperly using 'authorities').
Priorities for release
1. Content modeling
2. Flysystem to avoid duplicating huge files and give better control over where files go
3. Example migration (need not be from 7.x, but that'd be nice)
... (feel free to add agenda items)