April 3, 2019

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)
• Zoom link: https://zoom.us/j/203396828
• 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

• Daniel Lamb
• Melissa Anez
• Alan Stanley
• Eli Zoller
• Don Richards
• Jared Whiklo 🌟
• Marcus Barnes
• Mark Jordan
• Minnie Rangel
• Natkeeran
• Noella MacIntyre
• Rosie LeFaive
• Seth Shaw

Agenda

1. Testing Sprint
2. Should we consider using a Test Case Management tool such as http://kiwitcms.org/ or commercial/but free for os projects: testquality.com.
3. Documentation Sprint Loose-Ends
   1. Placing Blocks Documentation
   2. Metadata overview
   3. Views Documentation
   4. Drupal Modules
   5. Cheeseburger Replacement
   6. User Management
   7. Working with Content Types
   8. Adding a Media
   9. Create a Collection
4. Issue Roundup
   1. Default ports for vagrant environment
   2. Making Google compliant metadata
   3. Multi-site usage stats
   4. Debian Install?
   5. Competing with Sharepoint
5. Anybody considering using urls to represent dates/timespans: https://www.w3.org/TR/owl-time?; specially to describe mods:temporal/dcterms:temporal. Islandora MIG: MODS to RDF Mapping Recommendations is recommending that dcterms:temporal can "reconcile against a known vocabulary of temporal values". Would this be custom for each installation?
6. ... (feel free to add agenda items)

Minutes

1. Want to push back testing sprint by a week to give Danny some more time to get organized. That is if the people already signed up can accommodate moving back by a week. Danny will check with those already signed up.
2. Some work like this was done for 7.x and so for Islandora 8 we should develop some sort of test case management. This would be specifically for storing test cases for manual testing (ie. what to test and how to test it). We could possibly do this in a free way but that might make it overly complex to work with. Danny will look into the above linked options to set one up and give it a try. Nat offered his assistance.
3. We want to finish up some/all of these tickets and rebuild the documentation. Yamil offered run aspell against the docs once they are committed. If you can review one please do.
4. Re-order to #5, has anyone represented a datetime as a URL and what is the vocabulary of temporal values? Intention was to use LoC subject headings for timespans. No particular ones specified. Seth is using ones for temporal ranges for each century based on existing LoC subject headings. If you make your date as an entity, you could then re-use that date as a URI. Trying to avoid relationships so the metadata could be triples where the subject is the drupal node.
   • The easiest option, what we are doing right now, is to use a single literal for dates (EDTF packs the most date semantics we can get in a single literal).
   • Giving each date value their own URL could allow more complex date expressions using the time ontology, but this would require creating entities for each of them and ensuring they can be indexed in Fedora and the triple-store (requires a JSON-LD serialization and adjustments to the related Contexts if you aren't reusing Content Types or Vocabularies). Also, one may also want to redirect visitors to that URI to the relevant object if that particular date entity is only linked to a single item.
5. Issue Round-up
   1. Changing ports - Jared: We have a lot of documentation that specifies port 8000, might be easier to ask the 7.x vagrant? Or to use the switch suggestion? We would also have to update all the various ansible roles.