...
| Advanced Tables - Table Plus | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
Minutes
- 2015 Targets - next six months
Andrew
- 4.0 release greenfield
- 4.1 release - targeted for OR - get Fedora 3 to Fedora 4
Migration
- 4.1
- squash bugs
- new features
- Migration
- Establish pilots
- which features need to be migrated
- get many Fedora 3 institutions involved
- is documentation needed
- is tooling needed
- approach - in terms of objects
- use a connector, helps eliminates concerns
- connector talks to Fedora 3 REST API
- regardless of some configuration variables
- will simplify the transfer of assets
- need for parallel systems
- will need servers and storage
- can't do an in-place upgrade
- it's a migration, code base and storage
- In terms of messaging
- Software Upgrade
- Content migration
What do we tell people who want to stay with XML vs. RDF?
- You can't keep all forms of XML, like inline XML
- Fedora 3 audit trail, can become XML data stream, but not inline
Break out Fedora 3 features
- do some early analysis, what is going to be possible
- requirements for Fedora 3 to Fedora 4
- not fleshed out
- in training, did document considerations for upgrades
- security policies
- versioning
- disseminators
- how data and functionality map from 3 to 4
Migration Scenarios
- greenfield installation
- upgrade to Fedora 4 and replace functionality over time
- Hydra
- could have made Fedora 4 look like Fedora 3
- strategic decision to move to Fedora 4 approach
- continuum of migration options
- quick analysis to determine migration needs
- find common needs
- migration working group
- Migration Complexity
- consensus it will take time to determine scope
- Systems Administration
- Application Functionality, Compatibility, Refactoring
- Content Migration
- Hydra and Islandora - will be easiest community to migrate
- Penn State - looking at using Hydra as migration tool
- What is possible in the next 6 months?
- Moving Content to a new system
- can play with content, even if you haven't moved to a new system
- Have pilots
- working through migration
- specific features and capabilities
- content
- After 6 months
- have a few examples of sucessful migration
- Documentation
- things you need to think about in planning transition
- Hydra, Islandora, or Custom
Three Migration Types
- Greenfield
- Hydra/Islandora
- Custom
- Wild West
- Rebuild/Refactor - rewrite and ingest (Yale)
- New functionality - incorporate back into Fedora/Hydra
Promote the concept of community development when appropriate,
recognize and respect the need for institutions to locally customize
when required.
What if there are significant issues related to Fedora 3 migration?
- at some point the community will have difficulty in supporting
Fedora 3 beyond security patches
Migration consultancy
- At OR2015, have a room for migration support
"Upgration" - Migrate and upgrade - a new term
1. Survey
- collect information, quickly canvas the community
- identify use cases, common services and approaches
- keep as simple as reasonably possible
- some demographic data
- geography, size of installation
- intended for leadership group
- ship out after Monday January 12th
- get responses back by February 15, 2015
2. Establish Migration Working Group
- Code4Lib - awareness booth
- OR2015 - upgration booth
Actions