Skip to content

Commit

Permalink
Merge pull request #93 from NYPL/new-transfer
Browse files Browse the repository at this point in the history
Callout config and transfer pages
  • Loading branch information
nkrabben committed Jun 20, 2024
2 parents fe0d54e + 8f60a14 commit 881176d
Show file tree
Hide file tree
Showing 3 changed files with 49 additions and 9 deletions.
31 changes: 31 additions & 0 deletions _config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,3 +16,34 @@ heading_anchors: true

ga_tracking: G-4GBB05KF5M
ga_tracking_anonymize_ip: true

callouts_level: quiet # or loud
callouts:
# use for documentation still not fully complete, but partially launched
construction:
title: Under Construction
color: yellow
# use after launching new documentation for external staff, remove after some period time
new:
title: New
color: green
# use for legacy instruction that will eventually be removed, remove when documentation is removed
deprecated:
title: Deprecated
color: red
# use to callout requirements before starting process
important:
title: Important
color: yellow
# use for context to instructions
note:
title: Note
color: purple
# use for situations where no further work should be completed until situation is resolved
warning:
title: Warning
color: red
# use for final instruction or failure remediation
highlight:
color: blue

6 changes: 4 additions & 2 deletions transfers/Completing-transfer.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,10 @@ This page outlines the steps to take after transferring media.
(Refer to transfer instructions for the format you are transferring)

## Verifying all packages meet requirements
Under Construction
{: .label .label-yellow}

{: .construction }
packaging instructions to follow

* Run the packaging script

## Updating records in SPEC
Expand Down
21 changes: 14 additions & 7 deletions transfers/preparing-for-transfer.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,9 @@ This page outlines the steps to take before transferring media objects.
## Locating Carriers
* Carriers are located on shelving by the entrance door
* Carriers to be transferred are likely on `02.**` shelves
*
**Before a media object can be imaged it first must be recorded SPEC.**

{: .important }
Before a media object can be imaged it first must be recorded SPEC.

## Verifying SPEC records
An acquisition record should exist in SPEC and SPEC object records should exist
Expand All @@ -43,7 +44,8 @@ for each carrier being transferred.

* Select search

**Contact Collection Management if you cannot find the acquisition**
{: .warning }
Contact Collection Management if you cannot find the acquisition

### Verifying object records exist in SPEC
* Select the acquisition from the list
Expand Down Expand Up @@ -86,24 +88,29 @@ src="preparing-for-transfer/SPEC-object-records.png" />
* Confirm the number of items listed for Digital media matches the object records
* Report mismatch of digital media summary and object records to Systems and Operations

**Contact Collection Management if the number of carriers and records don't match**
{: .highlight }
Contact Collection Management if the number of carriers and records don't match

### Verifying additional carriers from Archival Processing
When archivists survey a collection they may find additional carriers in boxes.
Archivists should create object records for any carriers they find and notify
Digital Archives of their discovery.
* [Verify](#verifying-object-records-exist-in-spec) objects records exist in SPEC

**Contact the processing archivist if the number of carriers and records don't match**
{: .highlight }
Contact the processing archivist if the number of carriers and records don't match

### Handling Commercial Software
**These instructions are for Digital Preservation staff (including fellows) only.**

{: .note }
These instructions are for Digital Preservation staff (including fellows) only.
* Label commercial software with a simple acquisition name.
* `Crouch` for Stanley Crouch papers.
* Image commercial software only when specifically instructed to do so.
* Commercial software media don't receive objects records.

**When objects records were created for commercial software create an issue.**
{: .highlight }
When objects records were created for commercial software create an issue.

* Select issues from the object record menu in SPEC
<details>
Expand Down

0 comments on commit 881176d

Please sign in to comment.