Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Advanced Tables - Table Plus


TimeTopicLead
9:00 - 10:15Environmental scan review and feedbackDavid
10:15 - 10:30Break
10:30 - 11:45

Survey Discussions

  • Research Questions
    • e.g. What would it take you to migrate/upgrade to Fedora 4/5?
    • Get rankings and priorities, e.g. How much do you care about the repository back end of your service? How much to you care about the discovery layer of your service? how much to you care about the UI of your service?
  • Scope and scope creep. What do we really need to know? What can we find out that will be actionable? Do we need demographic info about size of repo or institution or budget? Do we need to categorize users?
  • How do barriers like budget, technology spec, product loyalty weigh in your decision?
  • Who do we want to talk to? Devs? Admins/DMs? Librarians? All Fedora users? Or just Fedora users who are super involved?
  • Cognitive Interviews - plans to set up calls to test survey in early Jan within and outside of advisory group. It will go through survey and discuss your impressions of it, e.g. did it get at what I wanted it to? Is there a question I missed? Is it too long? etc.
  • Dissemination
    • Personal recommendations for people we can talk to - advisory members as advocates.
    • Know our sample set - can we get all emails of people signed up to Fedora Google Groups and on our registry? And email them directly? That way we can know how many people it reached and a percentage of responses. Good metric.
Erin
11:45 - 1:00Lunch
1:00 - 2:30

Dissemination Plans

  • Open Repositories and other proposals and deadlines
  • Interim Communications - Fedora newsletters.

2:30 - 3:00

Scheduling preliminary consultations with advisory boards 

January next steps - tech review

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 - 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?

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 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. 

Actions