Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
July 12, 2017
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join. Here is the info:
- Time: 9:00AM 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
- 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
- Melissa Anez 🌟
- Diego Pino
- Caleb Derven
- Yamil Suarez
- Marcus Barnes
- Bryan Brown
- Natkeeran Kanthan
- Jared Whiklo
- CLAW Update
- Longer-view update for any newcomers joining for the new meeting time
- Install Sprint - highlights from the first meeting
- Basic Image issues:
- REST issues:
- Feel free to add more agenda items...
Meeting time has been moved to attract more people in Europe. Caleb Derven is our first success. Welcome Caleb!
- CLAW Update: CLAW can handle basic and large image functionality. Openseadragon viewer. Files flush to Fedora, but there is still a big update working its way through to make it all work properly. There's a theme, Carapace, made by Favenzio Calvo at FSU. It's on the sandbox and the vagrant. Everything in CLAW aims ot be as Drupal-y as possible. Content creation is done through the regular Drupal UI. Objects with many datastreams can be edited with a single data form.
Development has recently been on the theme. There's been work with integrating with API-X. It now works with a locked-down repository. API-X is a way of using rdf to align microservices with repo resources. There's an issue open to finalize this integration. Next up will be derivative creation. We've got editable forms. With that, we'll have the basics in place. After that, we look at some usability things, work with handling http requests, and long long view, we need to sort out how we're handling/storing XML metadata. Managing RDF mappings is not great from a usability perspective, so that needs attention.
- Community Sprints: The first sprint target is installation. Productive first meeting. Outlined minimum requirements to take part (and hour or two each week in planing meeting during the lead up, 3 days of work during the sprint), worked on setting scope and minimum requirements. Looking at bare-metal installations first, then containerizing. Maybe align long-term with the ISLE project. Danny has made an outline document to help make the case for institutions to assign resources to the sprint. It's open for comments.
It is not too late to sign on. Stakeholders can still sign on before the sprint starts, and anyone can attend the meetings through the entire process. A sign-up sheet is pending, once the outline doc is final.
- Basic Image Issues: We combined basic and large image, which makes sense as a module. But now they are pretty conflated, but they need need their own content types for display. We need to split them out so that we can allow different preservation masters. We'll end up needing two media types that are identical except for rdf mapping (display and preservation). All of these tickets could go together if some one wants to take them on - they make a good intro. Bryan is going to try to take these on. This is a good resource.
Diego asks if we really need basic image as a content type, or if we could just do this with viewers and a single content type.
Jared is concerned that we'd be fighting Drupal is we did it with rdf
Danny definitely open to exploring better ways to do it. We're re-using fields with entities references. We could certainly reference the same thing, but when you set the display, it will always been the same for objects of one content type. If you had mixed tiffs and jpegs, you might end up trying to use Openseadragon on a jpeg.
Bryan suggests letting the user choose the display.
Danny thinks that sounds good too, but we'd still need the different types to set that up. There is also the Context Module to explore.
Diego suggest looking as Display Suite as well.
Danny notes there's plenty to explore - but what we need at the end is to make sure that people can put what they need into the repo.
- REST Issues: When crating derivatives, we're going to need to explore some REST points. These are some simple issues to get things started. More complicated things are coming. Looking for the best overall approach, before anyone sinks too much time into this.
Final thoughts: Next whack of tickets will probably be about how we handle XML metadata. Jared has a pull request for CLAW vagrant that addresses some openseadragon stuff.