forked from alxp/islandora
-
Notifications
You must be signed in to change notification settings - Fork 118
Roadmap Meeting October 13th 2017 11:30 am AST
Mark Jordan edited this page Oct 13, 2017
·
11 revisions
*
This should be the Islandora Coordinating Committee Meeting, not Roadmap, but changing the title will change the link, which has already been sent out. Next time we'll get it.
- Chair: Mark Baggett
- Notes: Donald Moses
Per: Schedule
- Attending: Mark Baggett, Bryan Brown, Danny Lamb, David Keiser-Clark, Jonathan Green, Melissa Anez, Mark Jordan, Rosie Le Faive, Donald Moses
- Previous meeting notes
- Islandora 7.x-1.10
- Rosie preparing release candidate. Hoping to have a release on Halloween.
- Islandora Org chart
- Complex
- Most updates done live during last meeting.
- Mark Jordan can see about having a graphics person at SFU revise the drawing. Mark Baggett may be able to help with that as well.
- Code of Conduct- update wording
- Mark Jordan attended an event "It takes a village" - invite from Lyrasis. Bring together OS projects and discuss issues and strategies around sustainability of OS project. Highlighted the Islandora's community/structure as a good example. A report is expected as an outcome reflecting discussions and ideas presented.
- http://www.lyrasis.org/membership/Pages/IMLS-OSS.aspx
-
Documentation IG (Melissa)
- Have started to meet again. Monthly meetings being planned.
-
Dev Ops (Gavin)
- Meeting happening next week.
-
Metadata IG (Rosie)
- Met October 2 - notes here: https://github.com/islandora-interest-groups/Islandora-Metadata-Interest-Group/blob/master/Meetings/2017_10_02.md
- Question from Mark Jordan re: use of MODS without mapping within the framework and what the challenges might be. Discussion about storing of properties, raw MODS. Technical debt with previous migrations and creative uses of MODS extension element.
- Rosie: IG working to get more comfortable with tools to clean up MODS. Anticipating the need to do this to refactor and cleanup MODS. IG is collecting use cases and requirements.
- Examples: Recorded edited date makes sense in MODS XML, but not in graph represented in RDF.
- Danny and Jonathan both working on getting metadata into Islandora ... XML mapping.
-
IR interest group (Bryan)
- No meetings
- Security Interest Group (Rosie)
-
Oral Histories Interest Group (Kim)
- Group may be winding down.
- Met on Oct. 4
- https://github.com/islandora-interest-groups/Islandora-Oral-Histories-Interest-Group/blob/master/meetings/2017-10-04.md
-
UI Interest Group (Rosie)
- on hiatus
- Danny participated in a Fedora sprint.
- Call out for volunteers to start after the release and so far Adam S., Jon G., and ___ have volunteered.
- FCRepo specification review and draft coming by American Thanksgiving. Plan to ship CLAW with Fedora 5.
- APIx meetings/work
- 2018 Schedule has Halifax confirmed.
- David Keiser-Clark
- This week we completed the 3-week Public Comment Period. Thank you all!
- Current stage: Documentation + Planning, Prototype Construction, and LSAP considerations
- ISLE Steering Committee (David Keiser-Clark, Williams; Ben Rosner, Barnard; Steve Young, Hamilton)
- Update bi-weekly lightning meetings (open to all) scheduled for: 10/24, 11/07, 11/21 etc. through February 2018
- ISLE Updates group: https://groups.google.com/forum/#!forum/isle-updates (43 members atm)
- Mark Jordan
- Moving DOI framework forward but would love some feedback on https://github.com/mjordan/islandora_doi_framework/issues/7
- Plan to move from current IR at SFU to Islandora Scholar module
- Question from Mark Baggett: Any interest in ARKs for identifiers. Answer: Mark Jordan is looking at what might be possible. There are some specific DOI elements and that and the associated processes would need to be generalized. Mark Baggett to submit use case in the issue queue.
- Rosie Le Faive
- Working on IslandArchives migration.
- Chair: Donald Moses
- Notes: Melissa Anez
You may be looking for the islandora-community wiki · new to islandora? · community calendar · interest groups