Difference between revisions of "Improvements"
Jump to navigation
Jump to search
m (→Proposed) |
|||
Line 18: | Line 18: | ||
* [[Improvements/aippackage| AIP Packaging]] | * [[Improvements/aippackage| AIP Packaging]] | ||
** support alternate physical structures for an aip | ** support alternate physical structures for an aip | ||
− | * [[Improvements/aipreadme| Self Describing AIP] | + | * [[Improvements/aipreadme| Self Describing AIP]] |
** add a README file to Archivematica AIP's to make them self-describing | ** add a README file to Archivematica AIP's to make them self-describing | ||
* [[Improvements/warc| Web Archiving]] | * [[Improvements/warc| Web Archiving]] |
Revision as of 15:29, 5 June 2017
This page is intended to list possible new features, enhancements, and other improvements to any of the code used in an Archivematica based digital preservation system.
Proposed
- Disk Image Preservation
- improve disk image handling to better manage different file systems
- Containerization
- ability to deploy Archivematica into Containers
- DSpace AIPs
- Improve how AIPs stored in DSpace are handled
- Email Preservation
- improve email preservation workflows
- Islandora integration
- current status of Islandora implementation and proposed improvements
- CentOS/RedHat support
- ability to run Archivematica on an rpm based version of linux
- Developer Focused Documentation
- improve documentation for developers integrating with Archivematica
- AIP Packaging
- support alternate physical structures for an aip
- Self Describing AIP
- add a README file to Archivematica AIP's to make them self-describing
- Web Archiving
- extract metadata and files from WARCs for processing
- integrate with the Archive-It service
- Search
- improvements and changes to how AIP's are indexed and discovered
- Appraisal and Arrangement tab
- Possible enhancements to the Appraisal and Arrangement tab, introduced in v1.6
- Python3
- Google document with status
- Google document with other proposed projects and status
Completed
- Migrations
- Use Django's migrations instead of custom SQL-based migrations