-
Notifications
You must be signed in to change notification settings - Fork 71
May 25, 2016
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
- Melissa Anez
- Randy Fischer
- Jared Whiklo
- Ben Rosner
- Bryan Brown
- Nick Ruest
- Diego Pino ⭐ 🌟
- Cary Gordon
- DevOps
- Vagrant - Bleeding edge dev
- Ansible - Stable
- Docker - Stable
- Sprint updates
- ... (feel free to add agenda items)
- ####DevOps
Nick: Discussion of last week, we have a variety of ways of doing DevOps stuff in CLAW.
- Vagrant option/ using bash scripts
- Ansible
- Docker
Which leads to too much to maintain, so proposal is: Keep Vagrant bash scripts for bleeding edge functionality/deployment (daily development) and when "ready", release Ansible and Docker which will be updated to be production ready.
So "ready" means: Stable. Since we are moving away from the 2.x branch, Ansible and Docker will be updated when we have a minimal working set that can be deployed to something matching future.islandora.ca
Does that makes sense?
Jared says yes.
Diego yes also.
Bryan +1 for Vagrant as HEAD.
Ben yes.
Consensus on this!
Nick: regarding https://github.com/Islandora-CLAW/CLAW/pull/264, the move to separate Repos is close to be done.
DELETE is currently not working on PDX, will be handled in a separate pull. Problem related to individual depending-on micro services not registering their own TWIG template paths, so the main index.php (collection service) is only including it's own local paths on TWIG init. Fix is not complicated, being discussed by Jared and Diego.
Jared: We are setting the twig path in index.php, which is only good when you use one service. PDX depends on crayfish whose template path is not being set.
Diego: Do we have duplicate template names? We need to check because once we register all paths Twig will use the first found.
Jared: Check if we have duplicates, if so remove. New Review task: check all templates.
Nick: New issue? https://github.com/Islandora-CLAW/CLAW/issues/266
Diego: One way to avoid this is to prefix each of our templates with your service names.
Nick: Wants the work to be done, documented and people to be happy!
Consensus on twig template names, (prefix) and make each service provide it’s own local path.
Nick: anything else on 264? Is failing delete fixing a blocker?
Jared: No, lets merge and then apply the fix on crayfish and PDX
Diego: Merged 264.
- ####Sprint updates
- Randy Fischer gets a fresh update from Nick about what is being done during this Sprint.
- Other updates, Melissa did a lot of new Mascots for each sub-project, awesome!
- Drupal 8 Prospectus goes to roadmap this Friday, we will have news about this maybe next week.
- Nick is setting up some newbie tickets for next Sprint, like https://github.com/Islandora-CLAW/CLAW/issues/263
- And please provide some input on this (New Readme, work done by Melissa), if you have some time: https://github.com/Islandora-CLAW/CLAW/issues/261.
Nick: I migrated the use cases from fedora4 interests group to Claw.
Discussion: should Use Case labeled tickets be marked as closed or not if solved?
Nick will write something into https://github.com/Islandora-CLAW/CLAW/issues/252 and will close as resolved!
Bryan: Are there any other microservices that might get branched out in the future?
Nick: Derivative related micro services are one example of future development on this topic. We need to Discuss if we are approaching this locally as CLAW or in a more generalised way to be able to share or reuse archivematica/hydra with/from/to Islandora.
IIIF is also a concern and replacing Djakota. Some talk about how this works, what the options are.
Diego explains how the manifest JSON works and gives an example. http://www.e-codices.unifr.ch/metadata/iiif/laai-E-10-02-01-01/manifest.json
Nick talks about adapting current Vagrant to use/implement one of the many IIIF options.
Randy talks about the many problems related to using OpenJPEG (open source JPEG 2000) versus kakadu (hight cost) in an IIIF scenario.
###Drupal stuff
Diego: Drupal content discussion: what is the role of Drupal content? partial view? Complete 1 to 1 Fedora resource mimic?
Concerns about how Drupal manages content/entity/bundle definitions in database versus the need to have flexibility to handle a more dynamic reality coming from RDF.
Drupal 5,6,7,8 makes a static DB schema out of local contents. Once you added a field to a "content type" each consequent new content will have this as a field.
Some group discussion about how this affects our sync approach and daily ingest. Diego has this idea we could store whole rdf content coming from fedora inside a single field and use a widget approach to render/expose as form. But this would make filtering, exposing and using main Drupal functionality more complex. Maybe a mixed approach can be used, some base fields and also whole RDF inside one? Needs more discussion.
Ben: Expands on Diego's idea an explains this in good english! Basically if someone adds a new field to a bundle (and maps that to RDF) on drupal, all new contents based on that bundle will always have that predicate. We could deal with this in a custom controller, getting rid of fixed in schema fields if not needed?
Nick: Is for keeping fields mapped one to one to properties, also thinks Drupal content should be a view of the real RDF resource.
Jared: Explains our current plan (Jared+Diego) to make 2x entity types on the drupal side: one for RDF Resources and one for nonRDF resources, this way mapping back and forth is a little bit simpler.
Diego: Back Sync scenario is also a concern. If the content coming from fedora has RDF properties/types, etc, not defined on the drupal side, do we create those/append to the bundle or we only sync what exists was defined by the user in Drupal?
Ben: Offers help since he is developing/planning to do some entities work on Drupal 8 (and has a Drupal 8 book waiting)
This is also related to Multi site scenarios https://github.com/Islandora-CLAW/CLAW/issues/245
Top of the hour!
You may be looking for the islandora-community wiki · new to islandora? · community calendar · interest groups · roadmap