2022-06-09 Metadata Management Meeting notes

No announcements. 

Reach out to Charlotte Whitt  or Ann-Marie Breaux (Deactivated)  if you need to be added to the BugFest slack channel and given a TestRail account in preparation for the hands-on TestRail creation activity. 

Jenn Colt Laura E Daniels 

MM SIG Release Note & Other Highlights.

• 003 bug related to data import has been resolved. 
• Lotus Hotfix 1 release date has been pushed back to June 11. 
• Page includes a link to the MM Bug Tracker dashboard. 

Update and discussion of documentation at docs.folio.org

DRAFT Lotus documentation for Inventory and quickMARC

(MARC authority app documentation is up also but is still very much a draft)

---

docs.folio.org is where the official FOLIO documentation resides. It is heavily supplemented by the documentation on the wiki that is generated by the community. 

Documentation group has discussed adding links between the wiki and docs.folio.org, but there are no links yet. 

docs.folio.org, is consistent in style and is by release. It does not mention bugs or bugfixes. It describes what is and what can be done in this version. It also does not reference future functionality. 

Dennis Christman is maintaining documentation for data import and data export. Laura Daniels is maintaining the documentation for QuickMarc and Inventory.

About to release the Lotus documentation (soon after the Lotus release) and hope to have the Morning Glory documentation ready at the same time as the release of the software. This is a massive accomplishment and is due to all of the work of everyone who has contributed to development of the base documentation. Jesse Lambertson and many others have contributed to the creation of this documentation for metadata management in addition to Dennis and Laura. 

To access documentation for a specific release, you can use the release drop down menu in the header or add the release name before docs.folio.org (kiwi.folio.org). 

Request for feedback: please review the documentation and provide comments. Looking for feedback from people who are familiar with the apps and functionality as well as those who are new to the project. The documentation should be helpful for all of the users who will be using it. It would be helpful for users to provide the version (release) of the documentation to which the feedback is relevant.

Specific questions:

• (Inventory) Table of contents (TOC) is on the right. The page is very long, and the table of contents is long. Is this long because it is a lot of information and it is adequate, or is the length of the page and the TOC is an impediment to using the documentation and finding information?
• (Inventory) Is the repetition of information in each section okay? Chat comments suggest that repetition is helpful.
• (Inventory) Are there any changes that could be made to the order of the information in the page to improve the experience? Is the order acceptable or could it be better? (The order should follow the order of the elements in the edit mode and drop down menus. Please note if you see that this is not sometimes the case. 
• (QuickMarc) Much shorter than Inventory - please review to see if the order is useful.
• (QuickMarc) Author of the documentation is not using MARC holdings; if you are using MARC holdings, please pay extra attention to the details of the MARC holdings.

Question about keyboard shortcuts. A: There is a keyboard shortcuts is in left hand navigation as a platform essential. References to the keyboard shortcut to a function are not currently in the documentation at the point that the functionality is being discussed in other areas of the documentation. Laura mentioned that she could start doing this with Morning Glory. 

Question about documentation on Tags. A: Not currently. Maybe in platform essentials and in the apps / functionality documentation. 

MARCauthority should be a separate category and not under Inventory. 

How to provide feedback? 

• Would a form be useful? (Yes! Laura will create and share a form for the documentation.)
• Timeline: Documentation will be continually updated with each release, so there is no deadline. Feedback is always welcome. Feedback received by mid-release cycle would allow for incorporation of the feedback in the documentation for the next release, though this is an arbitrary deadline and not hard and fast.