...
Audio Conference: There is a Polycom speakerphone in the room, with phone number 301.827.7446.
Directions
For directions to NIH, maps and security information, see https://www.nih.gov/about-nih/visitor-information. If driving, you must enter at NIH Gateway Drive which is available from Rockville Pike southbound only. Nearby visitor parking is available for a fee. If taking public transportation, we are at the Medical Center stop on the Red Line.
...
Advanced Tables - Table Plus | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Actions
Notes
...
Introductions
Tim - Using Fedora for IR and special collections. Have been migrating for 3 years. Trying to do a lot in the migration process. Special collections will be Fedora 5.0 and we'll roll our own. We're use Hyrax for the IR. We're heavily oriented to preservation and less to access.
...
Scott - The technological side is missing from the environmental scan. I talk to storage and development people. I hear a lot about complexity and no one wants to be first and performance issues and configuration. List serve traffics is lots of messages about 'I'm one person and I need to stand this up fast.' Another motivation for us is an old product and unsupported software.
David - this grant will help us validate the reasons and get the data we need to support other related projects. We want to know what the best return on investment will be. We might have a lot of surprising information in this grant.
Mark - we migrated from CONTENTdm to Islandora 3 years ago. 1.3 million objects. We created the Move to Islandora Kit. Lots of metadata profiles. We will lose people if the migration isn't reliable. The process is driven by Drupal tooling not Fedora tooling. It's a different route. Anxiety in the Islandora community around Fedora 3 to the new models in Fedroa 4 - the way MODS or any XML metadata to RDF. We have an active metadata interest group. The data model in Fedora 3 - people are used to it and comfortable with it. It's ike an email with attachments. People can't see how that will translate to Fedora 4. Echoing the software is easy and people are hard. Communications piece here. Do people think about the Fedora. What do people know about versions and difference between. Categorizations.Prepare people to migrate every 3-5 years. How will that impact decision making? Framing migration as an ongoing process that's iterative between the 3-5 year process.
What about service providers? Do we need those? Users have money and not people. We're seeing that trend.
Tim - I could look at our file system and recreate it. There's comfort in that.
...
Tim - as we started looking at going to Fedora 4-5 one of our staff Ben Pennell did some testing to find ways to reduce the number of triples. There are ways to bring those down but there are trade offs.
...
Scott - research data is a big interest and that's where the money is going.
Environmental Scan
David - want to get a sense of what people are challenges with and why they are migrating.
...
Agile methodologies recommended. Staff turn over and single points of failure. Needed to define roles and create contingency planning.
Pause for discussion.
Survey Questions
- Importance of asking why institutions want to migrate
- If institutions are uninterested in migrating to Fedora 4/5 we need to know that
- Are institutions moving from Fedora to something else?
- Motivations may elicit more responses than barriers
- Key repository requirements
- What layer of the stack is highest priority? Discovery, UI, etc.
- When was the last upgrade?
- How often are you willing/able to do an upgrade/migration?
- Who makes/influences this decision at your institution?
- It may be unclear who makes/owns the decisions, which can itself be a barrier
- If you knew the migration would buy you X years before needing to do another migration would that influence your decision?
- Would the migration be worthwhile if it resulted in new skillsets that can be applied elsewhere?
- What if it resulted in a nicer interface? (Not as relevant with Fedora)
- What new affordances will the migration deliver?
- How many objects? TBs? Object models?
- What type of institution?
- What resources do you have to migrate and maintain a system? Developers, sys admins, etc?
- IT profile, capacity in house (how many resources can you dedicate?)
- We can get institutional data online
- What is your role? How much influence do you have over the decision to migrate?
- If you're currently on Fedora 3, what do you like about it? What do you dislike?
- What do you like/dislike about Fedora 4/5?
- If you're still using Fedora 3, why haven't you migrated yet?
- Ask a geographic question so we know where the respondent's university is and include institution name so we can dedup.
...
Things to consider
- Need to know how many people we're sending the survey to. Track percentage of responses
- Working with someone to draft and approve appropriate language for international audiences
- The focus of the grant is US institutions but we still want to reach out to the global community
- US institutions are impacted by activities and decisions in the global Fedora community
- Has there been any interest in maintaining and building on Fedora 3?
- Are some institutions happy with Fedora 3 and uninterested in moving?
- Who to include
- Service providers? Clients will follow their lead
- Decision makers
- Committers
- What does a migration cost? Can have a huge impact depending on how often migrations are done
- Survey should be 10-15 minutes max
- Interviews should help identify gaps/issues with survey.
Ideas
- Insider knowledge? communities of practice.
- are Are you willing to be the first? Tech adoption cycle.
- Importance of institutional and IT profiles. Categorizations
- Old product and unsupported software.
Communications piece here.
Do people think about the Fedora.
What do people know about versions and difference between.
- Anxiety of data models and schemas.
Prepare people to migrate every 3-5 years. How will that impact decision making?
Framing migration as an ongoing process that's iterative between the 3-5 year process.
What about service providers? Do we need those? Users have money and not people. We're seeing that trend.
Is tooling and training the best value? In terms of metadata and triples. Skill development.
- Size and complexity of the content. TBs and # of objects and content types data models (compounds) variety of metadata. Do you have content/complexity = small, medium, large. Important for diagnosis.
Cognitive Interviews. Volunteers:
- Este
- Mike
- Scott
- Tim (or someone at UNC)
Front End Application reviews. Potential ones:
- Samvara
- See action items
- Islandora
- See action items
Data
- Check with Doren
Existing migration tooling
- see grant for others
- Bridge 2 Haiku
- Metro consortium in NYC - Diego Pino?
Dissemination plan:
- OR? Yes let's try.
- CNI Spring meeting?
- DLF fall meeting?
- Preservation venues? PASIG NDSA SAA
- Partner/co-present with dspace folks?
- Publish (OR paper? C4L paper?)
- Channels for communication?
- Newsletter already there
- Survey
- be sure to follow up with recipients.
- dissemination - targeted.
- personalize the ask where possible, amplify with folks who have followers?
Potential ways to leverage results
- Could be used to create new proposals:
- Methodology and resourcing to help institutions get to a less precarious repository state
- Build migration tools and kits
- your idea here...
- Transparency about what's going on in the repository world
- archetyping barriers to upgrading repositories
- Busting myths (if there are any) so that there is clarity about those barriers
Actions
- Michael J. Giarloidentify potential front end candidates from Samvara community. Prefer PCDM and things that lean generalizable,
- Este Pope Poll community to look for Islandora folks who can be candidates. David Keiser-Clark?
- OCFL review Andrew Woods
- API spec review David Wilcox
- ALL: See conference check list and have everyone indicate what