2014-08-19 Meeting Notes DPIG

Date

19 August 2014

Attendees

Goals

  • The AWG Summary Report

  • Archival Description Working Group - goals, partnerships

  • Round robin (reports from conferences: Colleen's data curation workshop, SAA, etc.)

  • AIPS from Archivematica to DuraCloud - working with DuraCloud to get stuff into DPN

Discussion Items

TimeItemWhoNotes
Jenn
  • SAA - she saw some great stuff, new version of the SNAC project EAP-CPF
  • They've been working on a national repository for EAC-CPF records (not just harvesting but making a way for people to things in there)
  • Embedding digital objects in finding aids - session with Ellie, Northwest Digital Library (EAD Consortium)
  • Informal conversation with DPN with Carly Dearborn (Purdue)
  • There were notes about a couple of instances of ArchivesSpace and Islandora but not really
  • Personal digital archiving table/check in for the Austin Archives Bazaar
  Ladd
  • Webinar from Islandora next week on archives solution packs
  • First pilot with members September 1st (1TB, 10K bags, 3 of the 5 nodes, we will work with Texas A&M) - testing ingesting and replication, things will be deleted and then they will do it again
  • First opportunity for them to go through workflows, getting content into DPN from a member point of view
  • TDL is our front end for DPN and they'll be working directly with A&M
  • Some manual, some automated
  • The pilot goes for 3 months - uses one terabyte in a month
  • The results of the pilot will be presented at CNI in December
  • The Digital Asset Management Task Force - getting alot of people thinking about the things we think about
  • Adobe Experience Manager is doing a demo at today's meeting - supposed to do everything
  • Adobe's system actually uses from open standards and they are interested in talking about how to integrate Fedora with their slick system (better in terms of drag-and-drop than Drupal) Fedora on the bottom and Adobe
  • Ladd said "Hub!"
  Carlos
  • Big changes to IT staff at the iSchool - not sure
  • IT inventory management will be changing, which means purchasing will have to go through central IT
  • Administrative access to machines will be restricted unless you go through an elaborate exemption process - the ISO will be working on the training
  Jessica
  • Create a new list for an archival description working group
  Colleen
  • She went to ICPSR - workshop about managing data from start to finish, everyday they talked about a different phase of the data lifecycle
  • There was website for people that were part of a group
  • Colleen is willing to share the stuff - the folks were tech, faculty, data librarians, international representation
  • Data was scoped for survey data mostly
  • UTDR currently does not do any checking on the file when it is uploaded but ICPSR heavily curates the data it puts in - including checking that the numbers make sense
  • they have different lengths workshops
  • TDL is looking at using dataverse - they won't be able to deal with dynamic files, they can only deal with static files
  • Library can work with TACC to create a way to deal with stuff after a certain phase in the lifecycle
  • Preserving the dissemination side - TACC is soft money and they can't keep everything for ever
  Adam
  • Digital Archeological Record - one of a couple of repositories of record for archeological data in the US (mostly tabular)
  • Adam is dealing with data that is part analog, part digital, part born-digital, much of it is being transformed to spatial data or being transformed into database driven complex interfaces/objects
  • computationally based photography - extracting the geometry of a 3d object (think Autodesk app) - the resulting object is a composite 3d file consisting of 200 images
  • The archive of this stuff is enormous and poorly described, the meaning of this stuff is based on relations between things so we have a bunch of stuff and what do we do with it - dynamic data set that is only useful for the public in the future it has to be curated beyond file-level information
  • Adam and his colleagues are concerned because now that everything is digital - it is also the only record, you can't repeat the experiement, you already busted the sites
  • They put images in DAIS
  • They put some stuff in UTDR
  • They are working with TACC on some of the geospational/relational stuff
  • TACC working on autometadata extraction based on a naming convention that maps back to its location in a directory structure & database
  • Moving stuff on to IRODS
  • The TACC collaboration ran out of money, the new grant didn't get funded but they wanted to build a stand alone desktop app where you could drap and drop objects into it and basic Dublic Core would be applied close to the point of creation - mediating the transition of this stuff to a library system
  • With UTDR - they wanted to put original illustrations, text, fonts, etc. (the components of the final publication)
  • Came to a point where stuff was kind of working - DAIS, metadata by grad students (25K records), TACC running IRODS and database
  • TACC got some new money to work on visualization of directory structures - but there were issues putting everything on Corral - was moved to a VM where there was more access and some of their stuff is now being run by LAITS
  • DAIS is in stasis and the VRC Islandora is just one collection in DAIS, not the whole thing
  • Maria Esteva has been doing alot of work with tree structure analysis
  • Adam wants to get to a point where the library is actually managing the data
  • The interactive stuff they have has mabye 10yrs at most, but extracting data to attach tot he images and keep it somewhere where it can be preserved, hopefully, the library can take it on - especially the more the library is talking to TACC
  • Adam wants to publish the data - the idea is there would be an online companion (the data itself) to combine with the publication (the article) - you would be able to walk the path from the article to the data and from the data to an article
  • point of entry that is narrative and usable
  • Folks wanna get down to the item and then they want to zoom their way out "where was it mentioned" - the semantic web, you want the context but you just want a piece
  • bunch of money that has gone to linked data projects for coins - because they pretty much agree on coins
  • people want to point out to gazetteer or to an ontology
  • European conceptual reference model - archaeological items in museum collections - British museum did a CRM mapping of their collection
  • Reliable citation plays a role
  • URIs for every item in your database - reliable citation for the exact version that you provided
  • it's expensive - we need campus cost sharing and we need to create the infrastructure for it to scale
  • TDAR their costs are very high and they are just now getting spatial data figured
  • the modeling TACC does - they don't keep all of the products of that
  • 3D video files - this is the way that archaeology can be a science, if folks have the files, they can reproduce
  • In terms of proposing a model for implementation - the project directors want a solution and TACC wants to program; they haven't been thinking about anything webby - or pushing out code and constant updating
  • What do they need - Protege (basic complement for ontology building) Do we build a scaffold? Do we build a desktop project?
  • centralized schemata building - data
  • Open Context
  • TDAR - Adam is working with the guys from Open Context
  • ORCAT (sp?)
  • The issue with archaeology is that the "stuff" they work with, the actual materials they work with are extremely localized
  Katie
  • Lots of overlap between this archaeological work in classics and architecture
  • We need to be able to learn from what each other is doing
  • Jenn asks what about preserving archival information overlaps - linked data - embedding digital objects in finding aids > looking for overlaps
  • Meeting librarians have way

Action Items

  • environmental scan for complex objects on campus
  • get people in the room that have the same problem
  • Case studies for each of these groups
  •