Skip to main content

The Tidy Archive Catalogues project

The aim of the Tidy Archive Catalogues project is to enable archivist catalogues to be human- and computer-readable. We want to create a python package which will:

  1. enable researchers to analyse and visualise at the level of a catalogue or a subset of the catalogue that they find interesting.
  2. make checking for mistakes in archiving (typos, or non-compliance with archiving standards) easy for archivists, who work quickly and make many subtle decisions.

Road-map

The project currently aims to have the following functionality:

  1. Enable archivists to search their archives for potential typos/mistakes. Specifically, they will be able to be returned with: A. Specific places to check in the archive (e.g. specific reference numbers/codes, and columns) for mistakes, particularly for: i. Dates ii. Named entities (places, people, and businesses) B. Flag inconsistencies in the archive, according to a chosen set of archiving guidelines, for example if 'c.', 'c', 'circa' are used to mean approximately, offer one option. i. According to national archives guidelines ii. According to Theatre Collection guidelines
  2. Enable digital humanities researchers to digitally visualise/analyse the collection, by creating machine-readable and human-readable (for labels, etc) versions of the following c: A. Dates, date ranges, and date uncertainty B. Named entities (places, people, and businesses)

The output of (2.) should give the data in a useful format to interact with existing python/R libraries.

For example dates should be in a datetime format, places should be either points in longitude/latitude, or polygonal areas (e.g. in geojson), or easy to convert to. There should be tutorial notebooks, for creating simple visualisations of: A. Social networks B. Geographical areas C. Timelines

Both (1) and (2) should be tested on large archives (e.g. British Library and The National Collection), and smaller ones (e.g. The Theatre Collection, and the Harry Ransom Centre)

Contributors

Contributors are recognised using all-contributors guidelines.

Natalie Thurlby Julian Warren Jo Elseworth Elaine McGirr Emma Howgill

Metadata

Release files for tidy-archive-catalogues 0.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tidy-archive-catalogues 0.0.1
File Size Uploaded Provenance Actions
tidy-archive-catalogues-0.0.1.tar.gz 5.3 kB Without provenance Details for tidy-archive-catalogues-0.0.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tidy-archive-catalogues 0.0.1
File Interpreter ABI Platform Actions
tidy_archive_catalogues-0.0.1-py3-none-any.whl Python 3 none any Details for tidy_archive_catalogues-0.0.1-py3-none-any.whl

Total release size: 11.1 kB

Release files / tidy-archive-catalogues-0.0.1.tar.gz

Download URL tidy-archive-catalogues-0.0.1.tar.gz
Size 5.3 kB
Tags Source
SHA-256 checksum
How to use checksums
b5a904b41e031443ba18156d497a8aa9ad705be05635183c972f0555cd179721
BLAKE2b-256 checksum
How to use checksums
e1e5d87f744aacc6930a6df63437284726e9656ea27bbd6c9a75fc8a39e12120
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/2.7.15

Release files / tidy_archive_catalogues-0.0.1-py3-none-any.whl

Download URL tidy_archive_catalogues-0.0.1-py3-none-any.whl
Size 5.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cfcea243dba014e1196bfcf1fa36e2c64c5e50c4d7ee70b2353404d3cf1d012a
BLAKE2b-256 checksum
How to use checksums
5f0b3ca508dbe34dddbba36b3b1f15e420ef4be1757bde656a73578742922448
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/2.7.15

Security for tidy-archive-catalogues 0.0.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.0.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page