Page Comparison

• QuickMARC subgroup has met twice
  • authorities and biblios are under conversation have been talked about
  • holdings are next on the larger agenda
• data-import updates?
  • maybe update from Ann-Marie later

Would something like this page: Circulation Documentation - Needs be useful for MM? If so, how to organize? By workflow? By app? Other?

TO DO: next week – make decision about this

Documentation Group –

lessons of the day

• keep settings-related info in mind as part of documentation
• note expectations for future releases as such
• connect issues (JIRA) to the documentation
• FOLIO glossary in the works – use that terminology in the documentation (consistent vocabulary)
• use UI/screenshots as well as text
• unified style – using google team guide

Documentation drafting will take place in google; when approved will be pushed to GitHub

"Tips and tricks" part of wiki is not being updated as part of this work, but we should still contribute to that (needed in interim), some of that also may be migrated in future (Dennis will get clarification on role of tips & tricks)

Ann-Marie will keep adding to tips & tricks

question: how will updates be happening once the docs are in Github? (will need to be an ongoing process)

add link to Github docs at top of tips & tricks?

If you are creating features in JIRA, add link to documentation

Glossary terms: think about words that require disambiguation between apps (example: "note" or "check in")

MM documentation being broken into 4 point-people by app: Inventory (Jesse); Data Import (Dennis); Data Export (Robert); Lisa (quickMARC)

from chat and spoken by Charlotte (Again here - we need to be aware that we do not create a huge administration overhead. It needs to be easy to add updates. If getting an update in, is being time consuming, then we’re at risk that the Documentation get not updated. )

"

Maybe once base documentation is in, we could devote 30 minutes in MM SIG every couple weeks reviewing and identifying gaps/updates, at least until it's more complete" (Jenn)

maybe to add comments in the wiki for Documentation needs

from chat (For those of us managing Jiras, there are similar expectations about creating TestRail cases when the Jira is completed. I cannot keep up with those, so I use tags (labels) in the Jira issues to keep a running tally of tests I need to write. I can imagine doing something similar for documentation. Having some label so that I have a list of documentation that needs to be created/updated for newly-completed Jiras )

Mode of Issuance, Other Reference Data:

deviating from defaults (such as note types, identifier types, alternative title types)