Development roadmap: Archivematica

From Archivematica
Jump to navigation Jump to search

Main Page > Development > Development roadmap

Archivematica development roadmap

This roadmap describes what Artefactual is working on for the Archivematica system. Sponsored work, that is development of features and enhancements which is funded by our development partners, is prioritized. On our wishlist, we have also included enhancements and features that we would like to see or that the community has shown interest in; however, without development resources allocated to us or contributions from developers outside of Artefactual, we cannot guarantee their inclusion.

Reflecting the bounty business model for open source development, each feature is developed in partnership with an institution or group of institutions with unique workflow needs. Despite our best efforts to keep features as generic as possible, some extra development may be necessary for a feature to function well in your own environment. Please see the Archivematica services offered on Artefactual's website to find out more about how to become a development partner, get training and support, or take advantage of installation services.

We will issue public releases incrementally upon completion and testing of the sponsored features and enhancements listed below. All features are subject to code review and QA, the results of which may result in any feature being pushed to a future release.

Features by release number

Storage Service 0.7.0

Archivematica 1.4.0

  • Sponsored (University of Saskatchewan) Add post store AIP micro-service to let Islandora know that an object has been moved into storage and can be deleted from Islandora
  • METS refactoring and METS generation improvements
    • develop standalone Python METS reader/writer application and distribute separately from and integrated with Archivematica
  • Sponsored (University of British Columbia Library)
    • Sponsored Improvements to DSpace transfer
    • Sponsored Metadata only DIP upload - Issue #8039
    • This development will allow easier upload to ContentDM when access normalization is not required. The ContentDM Project Client will be used to load the digital objects to ContentDM, while the metadata upload from Archivematica will include the file and AIP UUID.
  • Backend - Not user-facing
    • logging
    • database ORM

Storage Service 0.8.0

  • Backend - Not user-facing
    • Sponsored (Zuse Institut) Changes to support AIP re-ingest
    • Replace Base64 encoding library with atob/btoa Pull request 55 #7698
    • Unicode/METS fix Pull Request 38
  • Improved Arkivum integration (proposed)
  • Update Django to version 1.7 or 1.8

Archivematica 1.5.0

  • Sponsored (Rockefeller Archive Center) ArchivesSpace integration
  • Sponsored (Zuse Institute) AIP DC and Rights MD Re-ingest Full AIP re-ingest requirements
    • Sponsored supports AIP versioning (METS file updates) #1564
    • Sponsored generate DIP from AIP after processing is complete - Issue #1843
    • does not support re-normalization
    • note that this work is only part of the entire AIP re-ingest feature, the rest is not yet sponsored
  • Sponsored (National Library of Wales)
    • Sponsored Add levels of description to Submission Information Packages using AtoM REST endpoint to enforce controlled vocabulary
    • Sponsored Generate hierarchical structMap in Archival Information Package METS file
    • This development is concurrent with AtoM development including the following: generate hierarchical arrangement based on METS structMap, map levels of description in hierarchical METS structMap to Level of description element in AtoM information object, and display hierarchical arrangement in AtoM treeview
  • Backend - Not user-facing
    • Update Django to 1.7 or 1.8

Storage Service 0.9.0

  • Dataverse integration (proposed)
  • Move some/all DIP upload responsibilities to SS (proposed)
    • Backend - not user-facing
    • move Index AIP micro-service to SS (proposed)

Wish list

This section describes enhancements and features that the Archivematica community would like to see researched and implemented; however, without development resources allocated to us or contributions from developers outside of Artefactual, we cannot guarantee their inclusion in an upcoming release. Also see unsponsored features/tasks/bugs without assigned releases: unsponsored and unscheduled fixes, features and tasks

Dashboard

  • User interface
    • Upload submission documentation during transfer upload #1910
    • Administrative dashboard interface for system monitoring, including status, restart services, maintenance of backups, tools for restoring, automatic indexing of ElasticSearch index
    • Indicator in dashboard of decision made at decision points
    • Indicator that Archivematica is currently processing
    • Status indicator to show current status of transfer/job
    • Reconsider icons and access to the Add Metadata / Rights templates (currently the icon matches the ‘report’ icon and it’s unclear when is the ‘right’ time to add metadata) and the Reminder: add metadata micro-service
    • Access tab, Archival Storage tab, Preservation Planning tab should have description of purpose of tab
    • Treat each tab as its own web application
    • Administrative access to Storage Service from Access tab
    • Task cogs containing no information should have a short descriptive indicator of why there is none (ie no tool output available)
  • SIP arrangement See also #6791
    • Visualization of transfer contents - #1578, Transfer and SIP creation#File visualization reporting page
    • Clean up of transfer backlog once arrangement is complete - in dashboard Admin? in Ingest?
    • Increase icon size and fix 'jumpiness' of content indicators
    • Include tooltips for buttons
    • Consider name change of 'originals' pane to 'transfer backlog search results' or the like
    • Create delete package request from Transfer backlog
  • Deposit tool
    • Configure transfer in GUI rather than in local filesystem for complex workflows (ie. adding metadata files, checksums, manually normalized content, etc)
    • Upload submission documentation (see above, may consider in Transfer dashboard tab)
  • Email ingest workflow
    • Improvements to e-mail ingest workflow (maildir)

Metadata

  • Capture PREMIS from external systems
  • Field validation in PREMIS rights templates - #1519

Format Policy Registry

  • Format Policy Registry (FPR) public site UI
  • Ability to send local format policy changes to the FPR public site #5074

Storage Service

  • Automated deletion of content in transfer source once a successful AIP has been created and stored
  • Ability to send AIPs/DIPs to duplicate locations
  • Re-index transfer backlog, AIPs and DIPs - ElasticSearch re-indexing
  • Ability to select multiple packages from SS to download at once
  • Persistent data about stored AIPs and DIPs
  • DIP generation/upload info logged to pointer file
  • SAMBA plugin for Storage API
  • Move ElasticSearch to SS
  • Research management of processing space, so a transfer cannot be run if it's too big for the allotted space

Integration

  • AtoM - Send PREMIS rights metadata with DIP
  • Hydra (Ingest, AIP storage, API plugin)
  • DSpace (Ingest, DIP upload)
  • BitCurator integration: packages, bulk extractor reporting, how much functionality/data can be integrated/re-used prior to Archivematica ingest #1869
Retrieved from "https://wiki.archivematica.org/index.php?title=Development_roadmap:_Archivematica&oldid=10295"