<rubric course="LIS654" name="repository">

<note>
  According to the syllabus, this assessment has a weight of 15/25 of
  the final grade.
</note>
<note>
  The objective assessed in all rubric criteria is Palmer Learning Objective 2.E.
</note>

<crit goal="2.E" id="value">
  <enun>
    cultural significance of items
  </enun>
  <level val="10">
    high-brow culture
  </level>
  <level val="6">
    items of popular culture
  </level>
  <level val="4">
    current items with low value, but with potential for the future
  </level>
  <level val="1">
    ephemera
  </level>
  <reason>
    The repository should contain digital-born or digitalized materials
    that have some cultural significance. 
  </reason>
</crit>

<crit goal="2.E" id="purpose">
  <enun>
    first page
  </enun>
  <level val="10">
    first page explain purpose and content types well
  </level>
  <level val="8">
    first page explain purpose but not content type
  </level>
  <level val="6">
    purpose is masked behind the interface
  </level>
  <level val="1">
    homepage of repository is confusing
  </level>
  <reason>
    The repository has a web home page. This page needs to be 
    clear to the occasional user.
  </reason>
</crit>

<crit goal="2.E" id="title">
  <enun>
    title
  </enun>
  <level val="10">
    title is telling 
  </level>
  <level val="9">
    title could be confusing
  </level>
  <level val="4">
    title is confusing
  </level>
  <level val="1">
    title is meaningless
  </level>
  <reason>
    A title is an important attribute of a repository.
  </reason>
</crit>

<crit goal="2.E" id="collections">
  <enun>
    organization into collections
  </enun>
  <level val="10">
    the organization into collection is meaningful and documented
  </level>
  <level val="8">
    there are collections, but the organization appears to be provider-driven
  </level>
  <level val="5">
    the organization of collections is confusing
  </level>
  <level val="1">
    there are no collections.
  </level>
  <reason>
    The organization of collections in the repository should be clear and user-driven.
  </reason>
</crit>

<crit goal="2.E" id="exhibits">
  <enun>
    organization into exhibits
  </enun>
  <level val="10">
    the organization into exhibits well done, and extensive documentation is added
  </level>
  <level val="8">
    there are exhibits, they are meaningful but not much work in spent on them
  </level>
  <level val="5">
    exhibits are not clear
  </level>
  <level val="1">
    there are no exhibits
  </level>
  <reason>
    The exhibits are pretty much the only way to get a narrative into the collections. 
  </reason>
</crit>

<crit goal="2.E" id="dc">
  <enun>
    DC metadata
  </enun>
  <level val="10">
    metadata is full to the extend of the reasonable
  </level>
  <level val="9">
    some metadata fields meanings are streched
  </level>
  <level val="6">
    some metadata that could be of use is not captured.
  </level>
  <level val="1">
    metadata is sketchy
  </level>
  <reason>
    It is important that the metadata is complete and correct, for the implementation of cross-repository search.
  </reason>
</crit>

<crit goal="2.E" id="tags">
  <enun>
    use of tags
  </enun>
  <level val="10">
    tags related items in a meaningful and useful ways
  </level>
  <level val="7">
    tags related items in a meaningful and useful ways, but some tags are singletons
  </level>
  <level val="4">
    many singletons and/or tags confusing and/or useless
  </level>
  <level val="1">
    tags are absent
  </level>
  <reason>
    Tagging is an important ways to put related items in an information system together. 
  </reason>
</crit>

</rubric>
