Jlderidder at 14:01, 30 September 2011

Jlderidder — Fri, 30 Sep 2011 14:01:00 GMT

←Older revision		Revision as of 14:01, 30 September 2011
Line 2:		Line 2:
	linking in of item-level digitized content.		linking in of item-level digitized content.

-	In September 2011 we changed our processes, per the [[https://intranet.lib.ua.edu/wiki/digcoll/index.php/Cross-Departmental_Focus DigiPres]] group decision (08/10/2011) to only store 2 versions of each kind of metadata	+	In September 2011 we changed our processes, per the [[https://intranet.lib.ua.edu/wiki/digcoll/index.php/Cross-Departmental_Focus DigiPres]] group decision ([http://www.lib.ua.edu/wiki/digcoll/images/6/62/Recap_DigiPres_20110810.docx 08/10/2011]) to only store 2 versions of each kind of metadata
	in the archive.		in the archive.

Jlderidder: New page: The workflow that incorporates the archiving of EADs is described in EADs, along with the pickup and dispersion into Acumen and the linking in of item-level digitized content. In Sept...

Jlderidder — Fri, 30 Sep 2011 13:55:42 GMT

New page: The workflow that incorporates the archiving of EADs is described in EADs, along with the pickup and dispersion into Acumen and the linking in of item-level digitized content. In Sept...

New page

The workflow that incorporates the archiving of EADs is described in [[EADs]], along with the pickup and dispersion into Acumen and the
linking in of item-level digitized content.

In September 2011 we changed our processes, per the [[https://intranet.lib.ua.edu/wiki/digcoll/index.php/Cross-Departmental_Focus DigiPres]] group decision (08/10/2011) to only store 2 versions of each kind of metadata
in the archive.

To quote the minutes:
'''We seem to have agreed to maintain an original and a current copy of each EAD and MODS file.''' The originals will be whatever is
picked up at the time of the snapshot, if they don’t already exist in the archive. Future snapshots at regular intervals (time
range unspecified) will check Acumen for more recent files. If the Acumen copy is not the same as the original, and there is no 2nd
copy in the archive, it will be added as the “current” copy. If there is a “current” copy in the archive, and the Acumen version
is different (and more recent?) the Acumen version will overwrite the “current” copy in the archive.

I've incorporated this logic (September 2011) into the storage software for EADs.

'''For each EAD deposited for upload, the script follows this reasoning:'''
# Is there an EAD file for this collection in the archive? (/srv/archive/ area)
## If not:
### this one is copied over,
### versioned to version 1, and
### linked into the Manifest
## If so, does this EAD match that one?
### If so: no action is taken. This version is already in the archive
### If not, is there a version 2 already in the archive?
#### If not:
##### This one is copied over,
##### versioned to version 2, and
##### linked into the Manifest
#### If so:
##### The existing EAD is backed up
##### This EAD is copied over
##### This EAD is versioned to version 2, and
##### NOT linked in (version 2 is already linked, because it exists)

[[User:Jlderidder|Jlderidder]]

Archiving EADs - Revision history

Jlderidder at 14:01, 30 September 2011

Jlderidder: New page: The workflow that incorporates the archiving of EADs is described in EADs, along with the pickup and dispersion into Acumen and the linking in of item-level digitized content. In Sept...