CNI 2016: Avalon overview
•Descargar como PPTX, PDF•
1 recomendación•502 vistas
Jon Dunn, Indiana University Evviva Weinraub, Northwestern University April 2016 Presentation given to The Coalition for Networked Information (CNI)
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (19)
Similar a CNI 2016: Avalon overview
Similar a CNI 2016: Avalon overview (20)
Más de Avalon Media System
Más de Avalon Media System (13)
Último
Último (20)
CNI 2016: Avalon overview
- 1. Avalon Media System Jon Dunn Indiana University Bloomington Evviva Weinraub Northwestern University CNI Spring 2016 April 4, 2016
- 3. What is Avalon? Open source software system that enables libraries and archives to provide access to audio and video collections • Hydra Solution Bundle • Goals: – Easily installable and configurable – Serve a variety of use cases and institutions – Create a basis for sustainable development
- 4. Why Avalon? • Existing repository systems don’t work well for time-based media – Issues: integration with streaming servers; hard to support time-based navigation; difficulties in integrating access control • Existing media systems don’t work well with repositories – Issues: focus on short-term access for teaching and learning; limited metadata and access control capabilities; integration with preservation workflows
- 5. Project Funding • 2010 – 2011: IMLS Planning Grant • 2011-2015: National Leadership Grant from the Institute of Museum and Library Services • 2015-2016: Andrew W. Mellon Foundation Partnership between libraries at Indiana University and Northwestern University
- 6. Goals of current Mellon grant 1. Develop additional Avalon functionality 2. Conduct studies of use of audio and video collections by humanities researchers 3. Develop and implement a community-funded business and governance model 4. Deploy Avalon in a hosted SaaS model for testing/pilot
- 8. Avalon Architecture Avalon Media System Archival Storage Authentic- ation LMS, websites ILS Hydrant Rails App All Users Desktop, Mobile Browser, Drop box Search Browse View Ingest Describe Manage Integrations Collection Managers Authoriz- ation Avalon code – consists of Hydrant Rails App and the Rubyhorn gem. Other pieces are leveraged. Users Fedora Solr Matterhorn Media Server Media Player (mediaelement.js) Can- Can Ruby- horn Hydra Head Black- light Omni- Auth
- 9. Release History • 0.1 – July 2012 • 0.5 – October 2012 • 1.0 – May 2013 • 2.0 – October 2013 • 3.0 – May 2014 • 3.1 – July 2014 • 3.2 – January 2015 • 3.3 – March 2015 • 4.0 – September 2015 • 5.0 – May 2016 • 6.0 – August 2016
- 10. Faceted browse via Blacklight
- 13. Embedding
- 14. Manage Content
- 15. Add item: Upload, Dropbox, or Batch
- 18. Access Control
- 19. Avalon Use Cases
- 20. Use Case: Archival Film
- 21. Use Case: Media Within Archival Collections 21
- 22. Use Case: Online Exhibits 22
- 23. Use Case: Online Publishing 23
- 24. Use Case: Consortial Licensed Video
- 25. Use Case: Video Reserves in Learning Management System
- 26. Use Case: Mass Digitization
- 27. Moving Forward
- 28. Lessons Learned from Advisory Board • Clearly define and focus on our core product • Ensure that Avalon is complementary to, not overlapping with, other solutions in the repository and media space • Keep the product as general purpose as possible to help drive adoption • For many institutions, modularity and ability to integrate with existing repository solutions is a key requirement • Partnerships should be chosen wisely • Reduce technical debt (e.g. keeping up with Fedora 4 and Hydra) is important for local installations • Integration with a variety of research and analysis tools will be important for scholarly uptake
- 29. Future Development Strategies • Migrating from Fedora 3 to Fedora 4 – Fedora 4 running with our current data model (so datastreams, etc). – Ensure no features in Avalon become nonfunctional during the upgrade • Avalon as a SaaS – Cloud deployment model – Working to develop partnership with Infrastructure Based Service companies – Interested in sites willing to pilot • Gemification of Avalon Architecure – Re-factoring Avalon code for paying off technical debt – Making Avalon components easier to install for other institutions – Re-architecting for full service and gems for other open source repository solutions – Building up from CurationConcerns • Creating a Robust Open Development Community – Using other open source projects as a guide – Potential introduction of Avalon Developers Conference to train and introduce code base to wider developer audience – Introduction of community based sprints
- 30. Community Growth New Adopters: University of Alberta University of Virginia Washington University, St. Louis
- 31. Questions? • www.avalonmediasystem.org • github.com/avalonmediasystem • jwd@iu.edu • evviva.weinraub@northwestern.edu
- 32. Discussion Questions • What other use cases do you have for A/V access? • What do you look for in adopting or investing in an open source solution? • What barriers do you encounter in adopting or investing in open source? • What factors influence your choice of SaaS vs. on-premise implementations?
Notas del editor
- Evviva
- Most repositories can deposit AV but the UX for ingesting and delivering is not optimal because you are providing the file to the user as a download. IF they are being used with a streaming system, they aren’t providing a secure access and can’t handle authorization. There are lots of delivery options, like MAM’s or online video tools like Kaltura but they are more concerned with immediate access. They aren’t concerned with long-term media access, they don’t support Library metadata standards, and they aren’t designed to support long-term preservation activities.
- Discuss motivations To fill this gap we identified. The planning grant really helped us identify this gap and to go after funding to support hiring of staff to build out these tools. The planning project talked with a lot other institutions to try to identify common needs and gaps. Conducted a series of surveys to focus the work of the project.
- One of the other goals of the grant is to work on Spotlight integration, but we’re exploring different ways we can deliver that functionality to be more flexible. Point 3 – Worked with Ithaka S+R to identify some different models for community supported technologies
- Jon
- Jon
- Evviva
- This upcoming release will be out last Fedora 3 release. It will provide a path for folks to migrate off Variations to Avalon (~11 institutions run Variations). The two major points for this release will be providing an ingest method (IU is currently in the process of ingesting our variations content into our production Avalon, ~10,000 of ~30,000 are currently ingested) and the playlist feature. Variations users will be forced to abandon Variations at some point in the nearish future because the next release of OS X will remove Quicktime's support for certain functions Variations need. These features have been deprecated for some time, but Apple is just now officially removing them. There also is not a supported version of Quicktime for Windows 10. So bad news for Variations but good news for Avalon adoption
- Mention that our migration to Fedora 4 at this point won’t be supporting PCDM, but we expect to work on that as we move forward. Watching Hybox as they go through some of these same issues.
- International Interest from Australia, Spain, Qatar, and Afghanistan. Also, there are a number of institutions using Variations Digital Music Library developed at IU back in the early aughts that we hope to work with to migrate to a future version of Avalon. IU will be making that migration this fall.
- Sandbox you can try out via the website.