{"id":2088,"date":"2023-02-15T02:28:44","date_gmt":"2023-02-15T02:28:44","guid":{"rendered":"https:\/\/sites.rutgers.edu\/alcoholstudies-archives\/?p=2088"},"modified":"2023-03-29T12:12:32","modified_gmt":"2023-03-29T12:12:32","slug":"one-day-at-a-time","status":"publish","type":"post","link":"https:\/\/sites.rutgers.edu\/alcoholstudies-archives\/one-day-at-a-time\/","title":{"rendered":"Digital Projects: One Day at a Time"},"content":{"rendered":"

\"\"The clich\u00e9 about eating an elephant one bite at a time is probably older than large digital projects, nevertheless, it applies to them too. For the Digital Alcohol Archives, I\u2019d rather pick the simple but effective quote in the title, One Day at a Time<\/em>, part of twelve-steps programs and inspirational texts<\/a>.<\/p>\n

By now, six weeks after its restart, the project seems to be slowly settling into the groove, with its components clicking together, even if only on a small scale. Each project platform has been properly set up and is working as they should. Each contains items uploaded in the past six weeks. By “uploading” I mean the whole process of selecting and locating the item, assessing quality, creating metadata, uploading and ingesting (to go technical for a second) the file into its final destination, double checking for errors, fixing if any, and religiously documenting above process, including a meticulously kept ledger with all data mentioned above.<\/p>\n

\"Screenshot<\/a><\/p>\n

The Ledger<\/h4>\n

The ledger is just a fancy name for a comprehensive excel document with worksheets dedicated to each of the four collections: Publications, Notable People, Summer School, and Special Collections. (Side note: The decision to split the large collection into smaller pieces is not new, it goes back to the very first version of the digital collection<\/a> presented on the CAS Information Services website<\/a> I created in 2008. The four parts were kept for all later versions, each of which hosted more content and was customized to its platform, among them this WordPress pilot.)<\/p>\n

Data Entry<\/h4>\n

Adding data to the ledger starts well before the item is uploaded. If there\u2019s a need for pre-approval by me or revision might be necessary for missing data (which is the case when our grad assignment will complete the actual process), the worksheet gives us the chance to review well ahead of time. Checked, corrected, amended, and approved, the records then can be more efficiently handled during the actual upload through RUcore\u2019s Workflow Management System. One record at a time, from start to beginning.<\/p>\n

\"Screenshot<\/a>

Nearly 300 items have been uploaded to RUcore by mid-February. Click image to see the most current count.<\/em><\/figcaption><\/figure>\n

Production<\/h4>\n

The individual columns partly follow basic metadata standards, i.e., anything that should be added to the metadata file, partly list production details, such as the date of revision and upload, file name and accession number, for each platform. Prepared before uploading, the first part makes the uploading process seamless (well, no need to check details, but upload errors still have to be fixed), while the production data not only keeps track of upload statistics but also allows checking items from multiple access points.<\/p>\n

The Process as a Whole<\/h4>\n

Finally, a word about the process itself. If it sounds like a done deal from what was said above, look at the title of this post. In fact, it\u2019s a painstakingly long process to upload every single record, with a lot of downtime between steps (i.e., while the system is churning and doing its magic to put the files where they are supposed to go). Each step is built on the previous one and the system freezes sometimes. It\u2019s incredibly easy to make a mistake during the metadata creation: the Commit to change button, which is used instead of Enter, can trick us, the radio buttons are way too close under one another for an accurate click, or one simply misses a field, and there\u2019s no error message to indicate that. Translation: you can\u2019t rush the process and you must pay attention to each field in each step in the Workflow Management System.<\/p>\n