Skip to content
Mark Jordan edited this page May 31, 2017 · 16 revisions

Time/Place

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

Attendees

  • Daniel Lamb
  • Nick Ruest
  • Jared Whiklo
  • Audrey Sage Lorberfeld
  • Rosie LeFaive
  • Will Conlin
  • Yamil Suarez
  • Mark Jordan ⭐
  • Kim Pham
  • Amanda Lehman
  • Ed Fugikawa
  • Jonathan Green
  • Robin Naughton
  • Don Richards
  • Favenzio Calvo
  • Bryan Brown
  • Adam Soroka

Agenda

  1. General update - What's new since last week?

  2. Mirador viewer (Jared)

  3. Entities vs. Nodes: What's the situation? (ELI5)

  4. Continuing discussions:

    • PHP Version Support Policy
    • Potential focus on install, containerization, etc.
  5. ... (feel free to add agenda items)

Minutes

General update - What's new since last week?

  • CLAW issue 643 (agenda item 3)
  • Mirador (agenda item 1)
  • Rosie reports that the the MODS/RDF mapping work will begin with the next CLAW call, and that the UX IG. Amanda reminds us that we should coordinate with the Hydra Mapping IG. Rosie, Jen Eustis will discuss.
  • Danny will reboot CLAW sprints after OR.

Mirador viewer (Jared)

  • Mirador D8 module
  • Above uses custom Mirador JS library - Jared warns that of our experience with OpenSeadragon, i.e., we use a custom fork.
  • UTLib's D7 Mirador module also uses a custom JS library. Kim summarized U of T's test results with the standard Mirador javascript library maintained by Wellcome Trust. Jared will follow up with Kim to get more info on these tests. Nick will talk to Esmé Cowles about his Plum implementation. Jon asked if we can continue to use OpenSeadragon, which is also IIIF compliant. Danny says all IIIF viewers are on the table, the community needs to prioritize which we focus on first. May make sense to start with Open Seadragon to get a proof of concept and move on from there. Question about sticking with the IIIF standard; Danny underscores that this is important to us (although there are four different IIIF specs: Image, Presentation, Authentication, Search). There are a few other viewers, like Diva.js.
  • Next steps: Jared will get a D8 field formatter working with OpenSeadragon, then move on to Mirador. Danny would love to demo this at OR.

Entities vs. Nodes: What's the situation? (ELI5)

  • ELI5 == Explain it like I'm 5: Favienzo said that discussion came out of issue https://github.com/Islandora-CLAW/CLAW/issues/644, leading to the theming question "are we using entities or nodes?"
  • Danny summarized the situation: He's now got a working first version. The end difference is that there is basically a lot less code now in the core Islandora module. The user experience is also now more consistent with stock Drupal (Content > Add content > choose content type). Also, nodes will work OOTB with most third-party modules.
  • Rosie asks how to distinguish between basic page or fedora objects. Danny offered a few different options, but says we haven't settled on any yet. We need more people to play with it.
  • Nick reminds us that Yamil and Kim's documentation will need to be updated to reflect this.
  • Disadvantage is that nodes are less flexible than entities, the typical Drupal "golden handcuffs". Better UX/Themer X, not as good DX. Example of "worse" DX is that we'll need to write/wrestle with our own REST API. But developers will find a lot advantages, many more than if using entities.
  • Rosie asks whether we can develop a visualization of that a CLAW object is? Just to help Islandora 7.x devs to understand what's coming. We already have this diagram. Adam offers that "being an object" is not as important in Fedora 4 as in Fedora 3. Fedora 4 doesn't have a strong notion of "object" like Fedora 3 does. Although Danny says that in terms of the D8 UI, there is a strong correspondence between nodes and their properties and F4 objects; example of this is that D8's media entities correspond to Fedora's non-RDF resources.
  • Rosie asks "so would i have 1, 5, or 50 drupal nodes to edit?" Danny responds that we use inline entity forms to edit multipart entities in situ.

Continuing discussions:

  • PHP Version Support Policy
    • Danny asked for a couple of people to spearhead our PHP version support policy. Balance: we need to remain relatively current but not leave users behind. Setting expectations before CLAW starts getting deployed. We also need to decide on our Java version support policy. Jon Green said he'd give it a first draft.
  • Potential focus on install, containerization, etc.
    • Sprint suggestions on these topic welcome - contact Danny.

Meeting ended at 2 pm EST.

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

⚠️ ARCHIVED Islandora Tech Calls

⚠️ ARCHIVED Islandora User Calls

Clone this wiki locally