Record Content Input Rules

  1. Record Content Input Rules every field in your system, i the same order as parts 3.3 and 4.1.  Write rules for each field Record Content Input Rules | Field Validation Rule | Validation Text Accessin the record. Do not copy AACR2R or RDA rules.
  1. Fill in this format for each field as follows:
  • Field name: spelled exactly as in Part 3.3 and 4.1 and in the same order.
  • Semantics: exactly as in Part 4.1.
  • Chief source of information: primary location of the data needed to represent the information object, usually in/on the object itself.
  • Input rules: prescription for how to enter data, including spelling, capitalization, punctuation, multiple entries, etc. Be sure to note if a field can be left blank.
  • Required? : Is this a required field in that must be populated with data in every record/representation in your system? For instance, “title” is a required field in most library OPACs, so every record must have a title specified. “Illustrator name” is not a required field, since many objects in a library collection do not have illustrators. Non-required fields may be left blank.
  • Repeatable? : Can this field be repeated in your record/representation? For instance will you allow more than one author field?
  • Unique? : Must the information in this field be unique throughout your system? A unique field would be one in which the data element cannot be repeated in this field in any other record in your system (e.g. accession number, record number, barcode number)
  • Example: list one or two data values from your objects. 4.3: Special instructions for Subject Related and Classification Fields:

It is possible that you will not need this section, depending on how you are designing your system. If this is the case, simple place “N/A” in this section.

However, if you have subject related field(s) you should include:

  • discussion of conducting subject analysis to determine subject
  • decision on how many terms to use
  • specific location to find the terms (your thesaurus or LCSH, etc.)
  • provisions for adding new terms if not in the controlled vocabulary
  • rules on capitalization and punctuation and order
  • rules on how to enter multiple terms

If you have classification related field(s) you should include:

  • type of scheme used (LC, Dewey, faceted). If faceted you also need to provide your scheme.
  • how to create the entire call number (general discussion of whether or not to use cutter numbers, work numbers, dates, etc.)
  • example of constructed classification number with call number elements 

PART V: Records for your objects

Using the field names you established in part 3.3 and the content and input rules you created in 4.2, construct records for your five sample objects. You can use a table to show the records or you can simply type the field name, followed by a colon, and then the value that would be contained in the field.

**Follow your rules precisely.** You might find at this stage that your rules need a little “tweaking” to work the way you intended. If this is the case, please edit them.

Your sample records should be presented in the same format as the example below.

Item #: 1040

Title: Where the Wild Things Are

Author: Sendak, Maurice

Illustrator:

Publication Date: 1963

Be sure to include all fields and the values that would be entered into each field for the five objects.  It is possible that one or more of the fields may not contain data. For example, if you are working with a website that has no date created information in the page source, then you would leave this field blank.  Be sure to follow your rules precisely.

Record Content Input Rules

 PART VI: Project summary/narrative

Section 6 is an opportunity for you to describe your experience with the project, including both positive and negative experiences. This section is a critical component of the report because it helps the instructor understand your experience this semester and improve the assignment for future classes.

Use this section to describe both your opinion of the outcome of the project and any problems you had in completing it. Because this may be the first time you have attempted the systematic organization of an information collection, you should expect to be confused or frustrated at times. Here you can identify problems you found especially difficult to deal with and discuss how you might construct your system differently based on what you now understand about the concepts and practices of information organization.

Tasks: Review your experience with and feelings about the project, such as:

  • Your reasons for choosing to organize this specific collection
  • Why or how your system is different or better than an existing or traditional system
  • Any major problems you had with representing objects in this collection
  • How you might construct your system differently based on what you now know
  • Problems you had with certain parts of the assignment
  • Problems overcome and skills learned
  • Whether there is a chance that you might actually implement this system for an operational collection.
  • How you will take what you learned from this assignment forward into a professional position.

The above is just a means to get you started reflecting on the project. It is meant to illustrate some questions you might address, but you may have other concerns and/or ideas to discuss.  This is open-ended; discuss any or all of the points above (or others). Because this is your personal assessment, you should write the narrative in the first person. Suggested length for Section 6 is 1 to 2 pages.