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. Push back testing sprint by a week to give Danny some time to get organized if the people already signed up can accommodate moving back by a week. Danny with check with those already signed up.
2. We should have developed some sort of test case management at this point working towards the first release. This would be specifically for storing test cases for manual testing. Could possibly due this in a free way. Danny will look into these options to set one up and give it a try with some coordination with Nat.
3. Finish up some of these tickets and rebuild the documentation. Yamil offered run aspell against the docs once they are committed.
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.
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.