2020-11-19 TAC meeting notes

5 min

Roll call

@Trevor Thornton

• Notetaker: @Andrew Morrison (Unlicensed)

• Next time (going alphabetically): @Dallas Pillen

5 min

Recent Contributions

@Trevor Thornton

Shoutouts since October!

• Listserv:

  • Rachel Aileen Searcy

  • Kevin W. Schlottmann

• Github:

  • Alicia Detelich

• Jira tickets:

  • Randy Kuehn

  • Jared Campbell
    
    

5 mins

Program update

@Christine Di Bella

• v2.8.1 release last week (incl. spreadsheet importer)

• v3.0 (focused on agents) release candidate in mid-December

• Not new accepting code, formal code freeze on December 7th

• New section of wiki: Anti-racism and Inclusion Initiatives

• Planning group for project to offer free hosting/training for under-represented groups

15 mins

Sub-team and Working Group updates

Integrations

@Dallas Pillen

• Held one meeting since last TAC

• Reviewing list of known integrations

• Planning to send email to mailing list promoting integrations early in 2021

Testing

@Rachel Searcy

• Tested Jira and Github issues for new release

• Performed complete system integration test

Development Prioritization

@Randy Kuehn

• Held meeting in past month

• 28 tickets created, 36 closed in the past month

• 66 created, 92 closed since July

• Only 3 bugs remain to be prioritized

• 89 feature-request tickets awaiting prioritization

• Held discussion with UAC yesterday

Metadata Standards

@Elizabeth Roke

• Working on establishing a process for updating metadata mappings in a more automated way.

• Exploring with API team on possibly adding metadata mappings in JSON.

• Improving documentation for non-archivist uses

Tech Docs

@Trevor Thornton

• Reorganized tech docs repo for three roles of implementor, evaluators, developers: https://github.com/archivesspace/tech-docs/tree/reorg_by_function

• Compiled list of static site generators to be tested

• Cleaning up documentation for latest release

API Documentation

@Trevor Thornton

• Work is happening, low visibility due to volunteer nature and non-TAC membership.

• Expecting contributions soon

15 mins

Discussion: What to do with the migration and metadata mapping documentation?

@Elizabeth Roke

• Metadata group discovered that different members were using different two different sources of documentation:

  • GitHub Tech-Docs repository:

    • https://github.com/archivesspace/tech-docs

    • Friendlier “GitHub Pages” version at https://archivesspace.github.io/tech-docs/

    • It includes:

      • https://github.com/archivesspace/tech-docs/tree/master/migrations which is the definitive version

  • The ArchivesSpace web site version:

    • https://archivesspace.org/using-archivesspace/migration-tools-and-data-mapping

• Should we move to one or better distinguish them?

• The version on ArchivesSpace.org is important for potential users when evaluating. But doesn’t need everything. Maybe add pointers to the other version.

• Does anyone think GitHub is off-putting for non-technical users?

• Some institutions block github.com, some may block github.io.

• Confusion over which version applies to hosted users and which to people running their own.

• ArchivesSpace.org version is a list of link. Some narrative text would be good for beginners.

• Who is responsible for each set of documentation?

  • ArchivesSpace.org managed by ArchivesSpace programme.

  • GitHub Tech-Docs (and this wiki) includes community contributions. It is managed by pull requests.

• Proposal: Move detailed information like mappings from ArchivesSpace.org to GitHub Tech-Docs, add more narrative text to web site, and link to details on GitHub Tech-Docs.

• Proposal: The ArchivesSpace.org version should be for managers wanting to know what it possible, the GitHub Tech-Docs version should be for developers implementing.

• Different styles are available for the GitHub Tech-Docs version, which will be tested for usability and accessibility.

• Register new domain name instead of archivesspace.github.io? Less intimidating and may avoid institutuional blocks?

• Proposal: Move Excel files to GitHub Tech-Docs for contributions and version control.

• Proposal: Metadata standards group should review documents, decide on conversion of spreadsheets to Markdown

• Conclusion: GitHub Tech-Docs is the version of record for TAC. Members should be encouraged to raise issues or create pull requests.

10 min

Open mic

User engagements committee has been advised that TAC is available to provide help.

5 mins.

Closing notes

@Trevor Thornton