forked from alxp/islandora
-
Notifications
You must be signed in to change notification settings - Fork 118
Coordinating Meeting August 28 2020 11:30 am AST
David Wilcox edited this page Aug 28, 2020
·
5 revisions
- Chair: Danny Lamb
- Notes: David Wilcox
Per: Schedule
- Attending: Don Richards, Melissa Anez, Danny Lamb, Mirko Hanke, Dara Virks, Amy Blau, Dan Aitken, Jeff Rubin, Bryan Brown, Janice Banser, Brandon Weigel, Rosie Le Faive
- Can we revive the Documentation Interest Group?
- Metadata IG (Rosie)
- IR interest group (Bryan)
- ISLE Interest Group (Gavin)
- Multi-tenancy Interest Group (Brandon)
- What do we do next, and when?
- Chair: David Wilcox
- Notes: David Kwasny
-
Previous meeting notes
- No comments
-
Master -> Main Rename
- Danny is working on this
- Lots of references in the documentation. Danny did a detailed find and replace operation
- Still references to preservation master files - do we need to change this?
- This comes from PCDM, Danny will bring it up with the editors
- Can we revive the Documentation Interest Group?
- Lots of documentation needs in Islandora 8
- Not enough participation to convene the group right now
- Getting some feedback on documentation from the new user call
- Looking for co-conveners
- What is the purpose of this group? What are the expectations?
- Make the documentation more cohesive, less scattered
- Identify gaps/needs. Not responsible for writing all the docs
- What is the workflow for finding documentation and suggesting changes?
- There is an edit button on the GitHub documentation page, but this requires the user to fork the repo, make the change, and submit a pull request back to the main repo.
- This workflow is likely to be intimidating to new users
- Docker lets users create issues to suggest improvements. Can we do something similar?
- DIG should establish a workflow
- Folks interested in joining or convening the group should confirm their availability and we will discuss at the next CC call
-
Metadata IG (Rosie)
- Met on Monday
- Discussed what metadata should do, types of documentation needed
- How metadata will be managed in Islandora 8. Who needs to see the metadata?
- Exporting and sharing metadata
- Using metadata to argue for whether or not we have enough stuff in the repo on particular topics
- Making sure it's not terrifying to edit, reflects and does not harm our communities
- Mapping based on getting as much out of MODS unambiguously - default metadata profile that makes sense
-
IR interest group (Bryan)
- https://github.com/islandora-interest-groups/Islandora-IR-Interest-Group/blob/main/meetings/2020-08-20.md
- Discussed results from Islandora Online breakout session
- Different types of access restrictions and how to build workflows
- New different ways that embargoes could work. What are some types of restrictions that people would want?
- Using Group in Drupal 8 to restrict access to roles/users but also roles within groups
- Motomo module has new owners
-
ISLE Interest Group (Gavin)
- Has not met since last time this group met
- Need a new liaison; Gavin is no longer on this call
-
Multi-tenancy Interest Group (Brandon)
- No new developments
- Survey results are in - total of 80 responses
- Not anonymized yet
- Tag will discuss later today. Use to set technical roadmap
- Version support timeline and big picture list of things to achieve
- Lots of low-hanging fruit
- Ranked in order of "yes" responses
- Batch editing of metadata
- Better documentation for migrating into Islandora 8
- Better documentation for customizing metadata
- Embargoes
- Collection based access controls
- Islandora 8 Accessibility Audit and Improvements
- Pre-installation documentation on everything you'd want to know before making a production environment
- Advanced boolean search as in Islandora 7
- Make migrating from 7.x more manageable
- A batch uploader that does not require terminal usage * Documentation on upgrading each piece of software in Islandora 8
- More written documentation for users * Auditing functions to ensure all background jobs completed successfully
- Collection management interface
- Integration for Google Scholar indexing
- What is an Islandora object?
- Good discussion leading to a Google doc: https://docs.google.com/document/d/1T-m10EERGvJNHME_J_iC_zPWeFQL2u1uK5JuH8Vikds
- Agreement on this would allow us to better construct a wizard for the UI
- Islandora is a community of people using Drupal as a DAMS. Lots of common practices for solving problems
- We can ship with defaults that show how flexible Islandora is but also easier to understand
- Melissa Anez is now a committer
- Making the development process more efficient
- Need more committers
- Enshrine in the workflow the Drupal concept of RTBC (reviewed and tested by the community)
- This would allow committers to use their judgment and merge pull requests on behalf of the community
- What do we do next, and when?
- Workshops (e.g. migration prep, metadata mapping)
- Could start with open office hours leading to a full workshop
- Livestream a migration? We could start with a small collection
- Workshops (e.g. migration prep, metadata mapping)
- Amy
- Nothing to report
- Brandon
- Nothing to report
- Dan
- Hoped to have a published version of the dgi IR stuff by now, hopefully in time for next meeting
- Dara
- Nothing to report
- David
- Had a successful Fedora Users Group meeting last week and another one coming up in a couple weeks
- Starting work on the IMLS Fedora Migration Paths grant work in September
- Don
- Nothing to report
- Janice
- Nothing to report
- Melissa
- Nothing to report
- Mirko
- New staff member who is a metadata analyst. She will participate in the MIG on an ongoing basis
- Rosie
- Nothing to report
- It would be useful to have people interested in documentation in the Islandora wiki that can be tagged with documentation pull requests
- Danny says we could establish and tag such a group
You may be looking for the islandora-community wiki · new to islandora? · community calendar · interest groups