Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Info |
|---|
For information on current and previous versions of Avalon, please see our the Releases page on Github. |
Release 6
January 2017 - Replacing Fedora 3 with Fedora 4. Feature parity with Release 5.
- Upgrades
- Fedora 4, Hydra 10, Solr
- New Models for Fedora 4
...
- Fedora 3- Fedora 4 Migration tool with reporting
Preparation for SAAS Pilot
...
- Set RuboCop profile as part of build
- Improve packaging
- Create ansible solution and docker containers (internal only)
- Better developer install methods
- Better OVA
Release 6.x
Spring 2017 — Bug fixes and improvements to 6.0.
- Easily Edit/Import Structural Metadata
- Player API
- Continued work on AWS integration/support
- Simplification of Development environment (e.g. nginx, ffmpeg transcoding)
Release 7
Moving to Hyrax/ Modern Hydra Stack
- PCDM support
- Exhibits Via Spotlight
- Spotlight integration and implementation
- How-to Documentation
- Strategy for QA
- Staffing and workflow
- Integrated Automated Test environments
- Remove RTMP Support
- Drop Flash
- Investigate HLS on all platforms and its implications
- Create one player view in Avalon
- Re-implement media element customization against the main branch
- Adjust streaming security model
- Move to standard mediaelement
- Better internal permissions setup
- Gemification/Break interdependencies
- Streaming gem for another repo app
- Bulk metadata/editing gem
- Structural Metadata Improvements
- granular seeking
- move a master file to a different item
- merge/split items
- Better local transcode support
...
Full feature list yet to be determined.
- Publishing Out to External Media Sites
- Dynamic Adaptive Streaming
- Deeper integration with Hyrax Community
- Further gemification/shredding of core components
Technical work to schedule:
- Improve unit testing
- SAAS solution
- RDF
- Implement PCDM
- Packaging/deployment, e.g. use of Docker. Improving installation experience.
- Scalability issues that may arise
- Automated functional testing
Unscheduled Features
- Facebook integration
- Reporting and metrics
- Collections based group management
- Collections based master file handling
- Internationalization
- Administrative metadata (owner, digitizer)
- Provenance metadata
- PBCore/DublinCore crosswalks
- Controlled Vocabularies
- Import media from other sources
- Image content/auxiliary items (how does Avalon fit with other initiatives?)
- Integration with oral history tools