Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated screenshots

...

  1. file: the path that the package/folder/file is located. If describing a restriction of the entire package, this will always be just "objects". In the case of folders or files you will list objects/ first and then the rest of the path. If your content is in a bag, you will need to put /data instead of /objects for folders and files so Archivematica looks in the correct place.
  2. basis: the basis of restriction, there are three choices we generally use: policy, statute. and donor ("other" is also an option in rare cases where a restriction does not fit those categories). In the event there is a copyright or license situation that should be noted, you would also have an entry for copyright or license.
  3. status: his field is only used for copyrighted content. This should always be "copyrighted" for copyrighted content.
  4. determination_date: the date you determined the statute applied to these records, most likely the present date. It is in YYYY-MM-DD format. This only used for restrictions with the basis: statute or copyright. It will allow us in the future to determine what version of the statute was in place at the time of the determination.

  5. jurisdiction: the jurisdiction where the statute or copyright applies, it is not used for the other restriction types. This will be entered using ISO 3166 alpha-2 country codes or subdivision code (often for states), most often used are "us" for United States or "us-ma" for Massachusetts.
  6. start_date: the start date of the restriction, if on the package or folder level, the oldest dates of a restricted file within the grouping. The start date of the copyright or license will be determined by relevant copyright law and/or donor or license agreement.
  7. end_date: the end date of the restriction often the restriction time period after the start date (the start date plus 50 years, for instance). If on the package or folder level, this will be the date plus the restriction period of the newest file with a restriction (newest file date plus 50 years, for instance). If the restriction end date is based on a donor policy reliant on an unknown end date (for instance the death of the creator), then this field should be left blank. The end date of the copyright or license will be determined by relevant copyright law and/or donor or license agreement.
  8.  terms: terms is only used when describing a license. This may be when a donor retains copyright to some/all of their collection but assigns a license for use to the content. The most common being Creative Commons licenses. For instance: "This content is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license"
    citation: the citation to the statute relevant to this restriction. This is only used with basis: statute. The most often used are FERPA, MA 201 CMR section 17, HIPAA, Attorney-client privilege, and Legal work product.
    Image Modified
  9. note: the description of the restriction based on restriction type. For example, "student records, restricted for 75 years". In regards to copyright and license, note any additional information as necessary.
    Image Modified
  10. grant_act: indicates the type of preservation repository action being described. For restricted content, this will always be "disseminate". For license/copyright it would be "use".
  11. grant_restriction: indicates whether the action in step 9 is allowed or not. For restricted content, this will always be "Disallow". For license/copyright this can be Allow, Disallow, or Conditional depending on the terms.
  12. grant_start_date: the same date listed in the first start_date field above.
  13. grant_end_date: the same date listed in the first end_date field above.
    Image Modified
  14. When finished, save a copy of file as a CSV in the “metadata” folder within the package you are transferring in Archivematica.
     

    Info
    titleNote

    If you have a bag where the “metadata” folder was created within the “data” folder or if you have not determined the restriction status because you are waiting to analyze the files in Archivematica, adding the restrictions metadata will wait until a later step in Archivematica and would only be for the entire package (see Archivematica processing step x under Ingest. (this still needs to be added to the documentation (link)). In the case of this type of bag, adding it to the metadata folder now would cause the bag to be invalid.


  15. Move onto the Creating and adding the metadata file section.

...