Eurovision archive strategies
•Transferir como PPTX, PDF•
0 gostou•428 visualizações
FIAT/IFTA World Conference, Dubai 2013. Technical Session. Preservation strategy and usage strategy is two interconnected strategies that tries to accomplish two very different things. Meaning you shouldn’t erode the structure of your data when new types of data comes in or when new projects want to do new things. The other way around: You shouldn’t be forces to implement your frontend applications restricted of your data structure. So it goes both ways. What we try to do. Is building tools between the two to allow mapping of data.
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Eurovision archive strategies
Semelhante a Eurovision archive strategies (20)
Último
Último (20)
Eurovision archive strategies
- 1. “Tools & strategies for Eurovision archive” Peter Overgaard Geckon Get in contact: peter@geckon.com Copyright © of this presentation is the property of the author(s). FIAT/IFTA is granted permission to reproduce copies of this work for purposes relevant to the above conference and future communication by FIAT/IFTA without limitation, provided that the author(s), source and copyright notice are included in each copy. For other uses, including extended quotation, please contact the author(s). #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 2. #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 3. USAGE / DISTRIBUTION STRATEGY VIEW STRATEGY INDEXING STRATEGY PRESERVATION STRATEGY #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 5. #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 6. Contest Event Person Song Country Artist #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 7. Contest Event Person Song Country Artist #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 8. Preservation Strategy • Harvesting data from Eurovision.tv api • Mapping to EBU Core using mapping tool • Dissecting content into normalized data structure API #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 9. Preservation Strategy 58 Contests & 74 Events 1320 Songs 1276 Artists 2298 Persons 78 Organizations 7034 Relations between objects #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 10. View & Index strategy Applications Webservice Search engine & Cache server Views / Index processing Metadata storage #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 11. Distribution strategy Files placed on ftp server for retrieval Metadata view inserted into MXF files Metadata storage #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 12. Examples • ESC Archive API search • ESC Archive search #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
- 13. Conclusion • Preservation, application usage and exchange have three very different metadata requirements • We have standards. So its now more about tools and strategies • Be aware of compromising your archive metadata structure between preservation and usage needs #FIATIFTADubai2013 Name of presenter(s): “Title of Presentation” (Keep it short)
- 14. “Tools & strategies for Eurovision archive” Peter Overgaard Geckon Get in contact: peter@geckon.com Copyright © of this presentation is the property of the author(s). FIAT/IFTA is granted permission to reproduce copies of this work for purposes relevant to the above conference and future communication by FIAT/IFTA without limitation, provided that the author(s), source and copyright notice are included in each copy. For other uses, including extended quotation, please contact the author(s). #FIATIFTADubai2013 Peter Overgaard: “Tools & strategies for Eurovision archive”
Notas do Editor
- IntroductionHi. My name is Peter Overgaard I’m the head of Geckon, a Copenhagen based company that manly focus on digital object management and I work with Danish Broadcasting Corporation on a range of digital archive projects. One of the newer projects is the Eurovision Song Contest Archive Project, where I’m managing the technical infrastructure of the projects. Meaning basically everything below the user frontend. The objective of this project can broadly be divided into two objectives: preservation and usage. - Collecting content from and about the Song Contest from all EBU members. Several contest recordings appears to be lost unfortunately. - Centralising all content of the ESC. Preserving this part of the European Television History. And finally Facilitating Access and DistributionSo essentially it’s a birth of an archive. I will talk about the process, tools and findings we have so far in constructing a new digital archive.
- Building a brand new archive from scratch involves a whole range of decision making. First entry into the data was this. Output from a webservice. Where we got access to available metadata from every contest year.
- The object models defines everything we build on top of it. The next step was to transform metadata from Eurovision.tv web service into the object model we defined. The obvious metadata standard choice for us the of course EBU Core as this is an EBU project. We worked with Jean-Pierre Evain on constructing the mapping between the imported metadata to the exported structure. This is usually a quite tedious pain staking job of manually mapping many xml fields to another structure. However using the metadata mapping tool we could work incrementally with Jean-Pierre on getting the mapping to EBU Core right.I did have some concern whether we would be able to map everything. Meaning if we would face that not all fields we want to map would have a suitable corresponding field in EBU Core. I was happy to find that EBU Core allows you to define your own fields. That really came in handy.
- After importing 58 years of Eurovision Song Contest we got these numbers. These is our core objects.
- Use is valueGather all the bits and pieces needed for specific use cases. So the buttom layer is obliviant of what we intent to use to.
- Use is value
- From structured data to no
- Each set of the metadata stack has different purposes, requires different strategies and hence tools to cope with the challenges of handling metadata for both preservation and flexible use.We have standards for storing, navigating and exchanging metadata. All will change over time. So its important you implement tools and strategies to handle this effectively. Preservation strategy and usage strategy is two interconnected strategies that tries to accomplish two very different things. Meaning you shouldn’t erode the structure of your data when new types of data comes in or when new projects want to do new things. The other way around: You shouldn’t be forces to implement your frontend applications restricted of you data structure. So it goes both ways. What we try to do. Is building tools between the two to allow mapping