Present: Lee Berry, Michelle DiMeo, Stephanie Lampkin, Cat Lu, Erin McLeary, Patrick Shea, Amanda Shields, Andrea Tomlinson, Jim Voelkel
Absent: David Caruso, Anna Headley, Hillary Kativa, Amanda Shields
Goal to get ppl from various dpts to have cross conversations and make decisions–inform various staff
Stephanie Lampkin intro, not even here yet!
Start having convos on standards, data, imaging, big picture stuff
Photo-Hillary's overview, recently created access database, been using 300dpi, may be interested in 400, cataloging in MARC, moved from object to folder/collection level
Jim-Rare Books: European standards for imaging to get funding (400 dpi) (FADGI Guidelines), imaging standards discussion likely at next meeting
rare book images from neville dig project, title pages of neville colelction, everybook wtih little exception has title page and maybe a few more images, more plates from interesting books (random)
technology changed, most valuable books imaged badly, good for reference still but otherwise worthless, 5000 nevile books, 3 images per book, thumbnail 15,000, images recorded in access database, filenames parsable, start off with bibrecord, loosely linked to catalog record with metadata, website collections separate, one off, legacy data/images, largely same images, few instances taken for magazine, jim's taken images personally, one offs given to andrea to upload to opac, shoots to highest res of camera, 70mb dropped 8mb, outside of neville about 1500 books, working on workflow where books are imaged every year when they come in, ask elsa for paperwork from neville project, bob? has spreadsheet on what each image is, andrea will look for it.
Erin-Museum collections, handout prepared by amanda, pp5 also document exhibitions, conservation and condition reports stored somewhere else, intern this summer surveying high/low res jpegs to determine concrete details, have a lot of assets in different places, don't have full control over, includes fine art, objects on website also one offs that were copy pasted by hand
jim's data, can write script to recover data, but messier. pp5 data has historical inconsistencies.
Patrick/Archives: accessioning-excel files, pp5 used for stamp colleciton and advertisements, haven't used in a while, no plans in future. accessioning moving into archivespace module moving forward. digitizing very rare outside of image collections, will do pdfs for access purposes to send offsite. processing for media kept with a/v formats. finding aids historically choosing local rules, moving forward marking up with ead, with minimal dacs requirements. accession spreadsheet will stay because of museum crossover.
Lee/Oral Histories: about 700 completed, 200 in various stages. all have digital component, each interview gets standardized file strcuture on P Drive. Pdfs, word files, mp3s, wavs, digital photographs. Had excel spreadsheets and access databases trying to capture info about all of these files–first spreadsheet then access, stopped sometime 2008, then relied on HighOrbit to keep tha tinfo and track OH progress. extractable from highorbit system–with chuck's help into access database, very hodgepodgy, cataloging as part of marc catalog, separately input into CMS.
Andrea/Archives/OH/RB: Opac 67,000 ind. title, 135,000 ind. item records, 165 archival records with FA out of 270ish, 38 image colelction records with pdf fa, 4,303 records from neville, with some title variation, use MARC, LCSH, original cataloging also shared on OCLC.
imaging, rights, and data standards all over the place across dpts, rights statements at least 3 diff ones.
Hydra Demo Links
Hydra is a DAMS, offers backend preservation, images will be checksumed for file integrity. ALso has rights/access management, linked data capability. Not out of the box solution, spanning all diff collections. Develop in house. Will be moving through project phases.
Digital Commonwealth (image collection), All HYdra has faceted browsing, using metadata we input. Data has geolocation, link back to catalog, creative commons, has page turner mechanisms.
UCSD
Institut del Teatre (museum)
John Hopkins Levy Collection - view PDF download function
short term plan, website launch in november with migrated data, as digital collections site, later to be replaced by Hydra.
Using website stuff as intro to Dublin Core - flexible, has been used for all different types of collections CHF has, can be broad,
Dublin Core - describes file and not whole book
15 core elements - Example Publishing element can include localized fields and repeat fields
Creator - person related to the creation;
Can some departments enter more information than others?
What will the workflow be? Jim- seems like a lot of work.
Cat: do you know some of the harder to catalog items? How would these map onto Dublin Core?
Blue items on spreadsheet - descriptive metadata, about the content of the collection item; Green is administrative metadata
New ID - digital object identifier URI issued by system
Rare Books - most won't be local guidelines, where do we pull controlled vocabularies?
Archives isn't wedded to what you've done - map
advertisements and stamps at item level - folder level on OPAC
Ask Erin - does she
Should Rare Books be a separate collection from library?
anna building server infrastrucutre, starting with sufia
next phase is starting with object ingest–dublincore template
next step is identifying core collection of about 50 objects, single image for ingestion
batch upload needs scripts for mapping, sit down to discuss top 50, level of data, thinking about basic elements
Jim: wants to see what's been done for rare books and dublin core
Measurements for rare books, various artifacts with different labels
Discussion on taking messy data and images not according to standard, do we move forward with things that don't meet guidelines? Having guidelines cross the board will help with grants and zoom functions.
Not all legacy stuff is unusable–photographs and some past perfect museum. Think through how to centralize workflow–digitization queue.
Patrick: object record of each file that is representative from each Finding Aid.
Jim: Could use the manuscripts that Penn digitized. Complex objects will have to wait for page turning.
For oral histories, how to control access to audio and full transcript.
Start with the sets, and come up with stats and how much time it actually takes to catalog and ingest.
Patrick: Plans for current CMS? no current plans for CMS.
Next step: go down list of fields and think what fields to capture, coming up with 50 things, probably first start wiht Hillary's image archives.
eventually could do a discovery layer that integrates catalog and digital collections–pros n cons to discuss. could also remain separate catalogs. the two searches, one searches website, other searches digital collections, could merge, but we want to use solr so likely won't be integrated.