Shared Print Actions Examples

The Shared Print Actions: Terminology (SPA) outlines usage of the 583 action note for recording shared print activities and contains many examples of usage. This page is devoted to examples of ways programs have implemented these guidelines. 

Note that many examples exist in the SPA document itself, which should be consulted first for usage. The following examples are simply for particular use cases that libraries have encountered for implementing SPA language. 

Also note that as of February 2025 OCLC is still in the process of updating validation of batch csv loads to validate '$d permanent' as allowed language. 

This page last updated February 2025. Send updates and other examples for inclusion on this page to info@sharedprint.org.

Monograph on shelf:

583 1# $a completeness reviewed $c yyyymmdd $f program $i volume-level $z on shelf $5 ___ $2 spa

Permanent Retention:

583 1# $a committed to retain $c 2025 $d permanent $f BTAA SPC $5 IaU $2 spa

Note that $d permanent is still being implemented by OCLC. 

Rolling Expiration Date

583 1 # $3 2024- or v. $a committed to retain $c 20240123 $d five years from receipt date $f FDLP PDT $uhttps://www.fdlp.gov/about-the-fdlp/new-limited-print-distribution-framework $2 spa

This usage is unusual in that there is no concrete end date. In general the spa guidelines require a $d in the 'yyyymmdd' format, though the Marc standards define the field as 'Time period which cannot be expressed as a specific date (e.g., at end of academic term or every six months)'. This usage conforms to that standard.

Discussions with the MARC Advisory Committee in 2022 on this topic resulted in the community generally using yyyymmdd with the acknowledgement that it is "wrong but fine" according to the marc standard.