-
Notifications
You must be signed in to change notification settings - Fork 6
2018 06 14 Board Meeting
Leah Prescott edited this page Jul 23, 2018
·
3 revisions
6/14/2018
Attending: Karin, Leah, Sean, Tobias, Tom
- Profile schema and METS schema changes were announced at the end of last week
- Added xsd:anyattribute to the agent/note element
- Have heard no comments back; if there are no comments by end of next week, will ask Glenn to go ahead and post to the LC website to officially publish those changes
- Leah looked at this and confirmed that the only endorsed schema that is "owned" by the METS Board in the METSRights schema
- Need to make sure it is in the Github repository
- Not clear in the rights schema that we are the owner - need to take control of it so everyone knows - will go through it at next meeting to see if anything needs to be changed or clarified.
- There will be a possible request to adjust the schema - some say they can't use it because they don't know who owns it.
- Need a place for people to request changes to the schema, parallel to our process for other schema changes. Tom will put it into a Github project. Need to figure out how to display information about the schema on the LC web page. The schema itself can be found on the METS Extenders page on the LC site (http://www.loc.gov/standards/mets/mets-extenders.html) and the direct link is http://www.loc.gov/standards/rights/ (postscript: Also now on Github at https://github.com/mets/METS-Rights-Schema)
- Review open issues on Github repository - Tom closed out issues that were years old
- Need to be better at putting issues in the correct repository - schema issues should go in the schema repository; profile issues in profiles repository
- Only broader issues that don't fit elsewhere should go in the generic METS Board repository
8 open issues in METS Board repo
#26 - New METS profile: Electronic Archive of Galician Heritage METS Profile
- Multilingual profile that prompted the xsd:lang changes to the profile schema
- Once that schema is officially published, can close out issue
#25 - Provide clarification of the METSRights schema
- Tackle at next meeting
#24 - Possibly add xsd:anyattribute to the agent/note element
- Close that out once change is published
#20 - METS OVerview XLink Examples Incorrect for Structural Links
#19 - Primer Xlink Issue
- These two are the same
- Schemas are correct, but documentation needs to be corrected - Leah will do that.
#18 - Find and post the template for making schema change requests
#17 - Creating Change Request template for schema
- Same issue - making template for schema change requests
- Want to use Github issue repository with a custom template as an interface
- Can only have a single template for all of the METS repositories - so particular schema would have to be specified in text in the template
#15 - Broken Link on METS Tools & Utilities
- Some of these links had been fixed; but they seem to be broken again
- LIMB software by i2s - they should be reporting to us, but we can be a little proactive.
- Leah will see what she can find out with i2s (post meeting - Leah contacted i2s and asked them to send correct links to Tom; have not heard back as of 7/23/2018)
- Tom, Karin, Juha and Bertrand will be going
- Karin's Powerpoint is a good starting point - tutorial made a couple of years ago. That tutorial was 3 hours and the conference workshop will be 3.5 hours.
- The PREMIS workshop proposal was not accepted.
- Not sure if there is a METS Powerpoint template - no consistent METS styling - for this presentation, should create something.
- There are graphics on the METS site on LC that could be used. Those graphic elements are already in Karin's presentation, but they should be made consistent on each page.
- Should we request that participants bring laptops? Not in the proposal for the workshop.
- Printout exercises - approximately 30 pages/person.
- Could put a directory listing for a small book up on a board, and then breakout groups could use that for the exercises - sketch out structure of METS document. Could include images of the digital object.
- Each trainer could also present their solutions and show possible differences.
- Also could show differences using different profiles. This would highlight the importance of profiles.
- Tobias and Sean may also be able to attend the conference.