Versions Compared

Old Version 9

changes.mady.by.user Valerie Addonizio

Saved on

compared with

New Version 10

changes.mady.by.user Valerie Addonizio

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Accomplishments

...

Start doing (green star)

Stop doing 🛑

Keep doing (blue star)

  • Increase community engagement

    • Reports out to the community via the listserv (i.e. we’ve done this, what do you think)

    • Engage ticket writers and commenters (invite to meetings, ask to work on specs)

  • Have Program Manger and/or Community Engagement Coordinator attend quarterly for questions

  • Presenting at the Online Forum

  • Develop a workflow for maintaining the importer/exporters sustainably. Suggestion to add metadata standards tags to tickets that require touching those files in the codebase. It is currently a major problem that Metadata Standards team members need to be able to partially read Ruby code to be a part of this group.

    • Put in document formerly know as Tiers of Support

  • Reminder of Action Items in email form

  • Explicit and helpful links in agenda and emails

  • GitHub File Watcher

  • Dedicated reading time in the meetings

Recommendations for finishing up this term

  1. Being included upstream - Valerie has drafted an email to be sent to the entire council at either the end of this term and/or the beginning of next term, plus I will explicitly mention it at the final TAC meeting this term.

  • Some of this feeling was generated after all the changes that came with 3.0, but we’ve moved forward on that concern forgetting that we were invited to participate and declined. So this is about aligning both our own expectations about our work and being included further upstream in changes.

  • This is a good example of where things that the metadata group should weigh in on are buried in specification documents and tickets.  Note that the specification includes a request to amend the EAD and EAD3 exports

  • Communicate it to Christine, the developers, but also TAC and Dev Pri.

  • More about a heads up than an approval process; fundamental to needing to track changes to documentation. Even if it becomes the primary job of this group to actively document and track those changes. We need to be tagged any time anything touches an importer/exporter

Rotating group of ex officio from Metadata who sit in on Dev Pri meetings

  • Elizabeth volunteers

  • Kevin volunteers

  • Our metadata rep for this term

Leadership for next term

Lead: Regine Heberlein

...