https://wiki.diglib.org/index.php?action=history&feed=atom&title=NDSA%3AMetaArchive%2FGDDP 2026-05-30T19:05:08Z Revision history for this page on the wiki MediaWiki 1.44.0 https://wiki.diglib.org/index.php?title=NDSA:MetaArchive/GDDP&diff=2309&oldid=prev 2016-02-11T19:18:21Z

<p>1 revision imported: Migrate NDSA content from Library of Congress</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 15:18, 11 February 2016</td> </tr><tr><td colspan="4" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div> </td></tr> <!-- diff cache key wiki_production-dlfwiki_:diff:1.41:old-2308:rev-2309 --> </table>

Dlfadm https://wiki.diglib.org/index.php?title=NDSA:MetaArchive/GDDP&diff=2308&oldid=prev 2011-03-28T12:53:50Z

<p>Posted initial draft of notes. Others invited to refine them</p> <p><b>New page</b></p><div>Notes From the MetaArchive/GDDP Presentation<br /> The presentation began with a general description of MetaArchive, its functions, financial commitments of members, and content management. <br /> <br /> ==Responses to Questions==<br /> ===What sort of use cases is your system designed to support? What doesn&#039;t this support?===<br /> *Small museums and libraries and archives who don&#039;t have large technical infrastructure. <br /> *Orgs that want to join a partnerships for long term sustainability. <br /> *Not people who just want to park content somewhere. <br /> *Not a secondary back-up more of a process to engage institutions to actively do work of data curation and preservation. <br /> *This is not a turn key hosted service.<br /> *Supports the storage and retrieval of content for members, not end users. Not an open access network. <br /> <br /> ===If we put data in your system today what systems and processes are in place so that we can get it back 50 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)===<br /> *Presenters suggest model speaks to this issue by striking the right balance between flexible technology without heavy administration. <br /> <br /> ===What resources are required to support a solution implemented in your environment?===<br /> *Required for support of MetaArchive – support for LOCKS software. <br /> *Central cloud infrastructure- key admin. <br /> *Having key reliable source of communication. To effectively curate your collection you need to have an understanding of your collection – how to document and store them. Document accumulation of files. <br /> *Concrete needs- some level of sys admin expertise, bring up a cache and run it. Tech specs layout what is needed. <br /> *Some level of programmer expertise for plug-in development to allow ability to add content.<br /> *Some sort of administrator for policy creation and curation. <br /> *Partnerships with institutions help build new directions for development.<br /> *Submission Information Package necessary for ingest. SIPs require a great deal of work to create for any system. Advantage of MetaArchive is that exactly what the work entails is clearly defined for members. <br /> <br /> ===What infrastructure do you rely on?===<br /> *A slate of open source tools Linux, Drupal sites, Google code repository, plug-ins in development, TRAC. <br /> <br /> ===What types of materials does your system handle? (documents, audio files, video file, stills, data sets, etc) And give examples of those types in practice===<br /> *Content needs to be web friendly – crawl-able not necessarily html otherwise agnostic to formats. Will take anything.<br /> <br /> ===How can your system impact digital preservation activities?=== <br /> *Focus on distributed digital preservation.</div>

Trow