The acquisitions interface is a Javascript application for allowing workers to add acquisitions and accession records into the ldr. In order to facilitate that purpose it has three major sections

1. An acquisition form submission page
2. An accession form submission page
3. A list of accessions

As extra information, there is:

1. an about page describing

• how each type of user should use the site
• a FAQ list

2. a list of accession records

1. Be a location for SPCL users to enter data about new resources about to be added to the LDR
2. Be a location for SPCL users to review data about resource that have been added to the LDR
3. Feed data entered by SPCL users into a central database of information about resources in the LDR

The acquisition record is the one that a student worker fills out. It contains 56% of the information record in the accession form.

The main purpose of this form is to provide a rapid means for the student worker to submit new resources to accession into the LDR. This form is then picked up by the Digital Accession Specialist in a list.

It has the following fields:

• accession identifier = must be four numerals followed by a dash followed by three numerals
• collection title = must be a string ending with the word "Collection"
• receipt letter info required = may be True, default is False
• receipt letter info sent = may be an ISO-0601 formatted date
• gift acknowledgement info required = may be True, default is False
• gift acknowledgement info received = may be an ISO-8601 formatted date
• organization = must be a department in the university. Will most commonly be Special Collections Research Center
• origin description = may be 1 or more sentences
• administrative comment = may be 1 or more sentences.
• a list of donors for the material = must be 1 or more individuals, a. a first name b. a last name c. an email address d. a phone number e. a mailing address
  • street address
  • unit number
  • city
  • state
  • zipcode
• a list of sources for the material = must be 1 or more individuals, a. a first name b. a last name c. an email address d. a phone number e. a mailing address
  • street address
  • unit number
  • city
  • state
  • zipcode
• a list of restrictions applied to the material = must be 1 or more lines a. a formal SPCL restriction code b. a description of why that code was applied
• a list of the physical media and how much of each that medium that holds the resource originally = may be 1 or more lines a. a descriptor (e.g., floppy disk, cd, thumb drive) b. a number reflecting the amount of that descriptor that was in the accession
• whether it is a mixed acquisition = must be Yes or No

1. Select whether this is a mixed acquisition or not
2. Enter an accession identifier
3. Enter a collection title: this should be a close approximation to a formal collection title
4. Check if a receipt letter is required
5. Check if a receipt letter was sent
6. Check if a gift acknowledgement is required
7. Check if a gift acknowledgement was received
8. Enter the name of the organization that is creating this record
9. Enter a description of the origin of the resources. Was this from the Universaty Administration? From IT Services? What are the issues around this origin?
10. Enter any extra information that the user thinks the DAS neesd to know
11. Add 1 or more donors
12. Add 1 or more sources
13. Add 1 or more restrictions
14. Add 1 or more physical media components

Either of these forms are reached from the accession or acquisition form. Clicking on the link for a new donor or a new source from either of those pages opens up a new window with the appropriate form.

They have the following fields

• first name
• last name or
• instution name and
• phone number
• email address
• mailing street number and name
• unit number
• city
• state
• zipcode

1. Enter the donor/source's first name
2. Enter the donor/source's last name
3. Enter the donor/source's phone number
4. If ther donor/source has more than one phone number, click on the "add" button next to the label for "Phone number" and fill in the form field that appears
5. Enter the donor/source's email address
6. If ther donor/source has more than one email, click on the "add" button next to the label for "Email address" and fill in the form field that appears
7. Fill in the mailing address including street number and name, if there is a unit number, the city, state and zip code.
8. If there is more than one mailing address, click on the "add button" next to "Address" and fill in the form fields that appear
9. Click "Save"
10. If the form is complete, the window will close and the Accession/Acquisition Form Page from which you temporarily were navigated away will reload the appropriate data list for Donor or Source.

This form is reached from the accession or acquisition form. Clicking on the link will open a new window with the appropriate form.

It has the following fields

• media descriptor
• quantity of the media

1. Enter the descriptor label
2. Enter the quanity of the physical media present
3. Click "Save"
4. If the form is complete, the window will close and the Accession/Acquisition Form Page from which you temporarily were navigated away will reload the physical media data list.

Possibility to install this interface into Wagtail. This would require

• developing a custom wagtail page type for the accession and acquisition forms

• develop a streamfield for listing ajax items

  • would have to be able to list acquisitions with the required data
  • would have to be able to list accessions with the required data

• all custom page types and streamfields be useable by everyone who has write access to the library website see wagtail doc for streamfileds and block types

• a wagtail page type would need to be developed to hold the form and various data lists that need to be on the page for each form (see wagtail doc for page blocks

• would need to develop a form for the acquisition and accession in wagtail see wagtail doc for forms

• wagtail has an api that can be extended see api doc

Of potential use, though I don't see the immediate use case right now, is that wagtail has a read-onlyAPI see the api doc