Metadata Profile for HCI /depot
The table below shows the metadata application profile (MAP) for the HCI /depot collection, which will help you understand how to structure and categorize data in this collection for future additions.
For more details about this MAP, see the project’s documentation. You can also explore the full metadata schema used in this collection on Google Sheets.
Element Name | Dublin Core Mapping | Obligation | Cardinality | Input Guidelines | Value/Syntax Schema | Examples |
---|---|---|---|---|---|---|
objectid | Identifier | Mandatory | 1 | Use format: capstone_[YYYY]_[XXXX] , where YYYY is capstone project completion year and XXXX is the student’s full name. Make sure to separate the names (first, middle and last) using underscores. |
|
|
parentid | Relation | Optional | 0..1 | Include for objects w/in a compound object. Should appear as the objectid of the compound object in which it is contained. |
|
|
filename | Identifier | Mandatory | 1 | This is the poster's file name. Must exactly match the actual filename of the file in the “objects” directory, including the case of the filename and file extension. (Quick tip: When adding new files, it’s a good idea to rename the file and follow the format: capstone_poster_[YYYY]_[XXXX].[FILE EXTENSION]. This will help keep the data consistent and organized on the backend). |
|
|
format | Format | Mandatory | 1 | se media types format on IANA to describe the capstone poster’s file type:
|
IANA Media Types |
|
title | Title | Mandatory | 1 | Enter the capstone project’s title exactly as it appears on the poster, using the title case (capitalize the first letter of each major word).
If the title includes special symbols (e.g., + or “” or ?), include them as they appear. If there are multiple projects with same name, differentiate the new one by adding the year in brackets. |
|
|
creator | Creator | Mandatory | 1 | Use this format to add student’s name: [FIRSTNAME] {[MIDDLE NAME]}] [LAST NAME]. Make sure write it in title case. If multiple student creators, separate by comma (,). If a student has a single name, just write that name. |
|
|
description | Description | Mandatory | 1 | Briefly describe what the project is about in 1-3 sentences. Use clear, complete sentences. This can usually be found next to the project title on the poster. |
|
|
course | Course | Mandatory | 1 | Use format: XXXX [Course Name], where XXXX is the course number. Make sure that the course name is written in title case (capitalize the first letter of each major word). |
|
|
date | Date | Mandatory | 1 | Use format: YYYY, where YYYY is four-digit project completion year. Don’t add any months or dates. | W3 Date and Time Formats |
|
term | Coverage | Required (if available) | 0..1 | Add the duration of the capstone course. If it was only one semester course, just mention one semester with year. Make sure to write in title case - capitalize the first letter (Fall, Spring). |
|
|
thesis | Relation | Required (if available) | 0..1 | Include the file path to the digital documentation, available in pdf format. Make sure to enter the correct file path. Use format: /hcidepot/objects/thesis/capstone_thesis_[YYYY]_[STUDENT’S NAME].pdf (Note: This file needs to be stored under thesis folder in objects). |
|
|
capstone_advisors | Contributor | Mandatory | 1..n | Use format: [FIRSTNAME] [{MIDDLE NAME}] [LAST NAME]. Make sure to write it in title case. If multiple capstone advisors involved, separate by comma (,). |
|
|
associate_instructors | Contributor | Required (if available) | 0..n | Use format: [FIRSTNAME] [{MIDDLE NAME}] [LAST NAME]. Make sure to write it in title case. If multiple associate instructors involved, separate by comma (,). |
|
|
prototype_link | Relation | Optional | 0..1 | Include a link to any digital prototype, demo, or related external media. Make sure to enter the full URL starting with http:// or https://. |
|
|
project_type | Subject | Mandatory | 1 | This information should be derived from the project’s context. This will usually be mentioned in their documentation. | See § Project Types in Project-Specific Controlled Vocabularies. |
|
project_theme | Subject | Optional | 0..n | This information should be derived from the project’s context. This will usually be mentioned in their documentation. | See § Project Themes in Project-Specific Controlled Vocabularies. |
|
industry_application | Subject | Optional | 0..n | This information should be derived from the project’s context. This will usually be mentioned in their documentation. | See § Industry Application in Project-Specific Controlled Vocabularies. |
|
user_groups | Subject | Optional | 0..n | This information should be derived from the project’s context. If multiple, separate by semicolon (;). | See § User Groups in Project-Specific Controlled Vocabularies. |
|
degree_book | Relation | Optional | 0..1 | TInclude the file path to the graduate degree book, available in pdf format. Make sure to enter the correct file path. Use format: /hcidepot/objects/books/capstone_grad_book_[YYYY].pdf (Note: This file needs to be stored under books folder in objects). |
|
|
source | Source | Mandatory | 1 | Enter the school associated with the capstone project. This can typically be found at the bottom of the project poster. Make sure to write in title case. |
|
|
subject | Subject | Mandatory | 1..n | Provide keywords for the project, separated by a semicolon (;). Make sure that keywords are relevant and concise. These can include technology names, specific tools, methodologies, or other terms that help describe the project’s content. |
|
|
language | Language | Optional | 0..n | Specify the language of the project materials in format xxx. Follow 3-letter codes for ISO language names. | See ISO 639-1 3-letter Language Codes |
|
rights | Rights | Mandatory | 1 | Provide a free-text description of the rights, typically “student retains copyright.” You may start it with the copyright symbol (©). |
|
|
rightsstatement | Rights | Mandatory | 1 | Provide a URI-based rights statement. Usually, students will hold the copyright over their work unless otherwise specified. | Rightsstatements.org |
|
display_template | Format | Mandatory | 1 | Specify pdf or jpg depending on the capstone poster’s file type. |
|
|
object_location | Identifier | Mandatory | 1 | Use format: /objects/[poster filename].pdf (Note: This file needs to be stored under objects folder and should match the exact file name). |
|
|
identifier | Identifier | Optional | 1 | Use format: [Name of the physical place]_objectid |
|
|
image_small | Relation | Mandatory | 1 | Use format: /objects/small/[poster filename]_sm.jpg (Note: You need to add this file path here so that these images can be generated using rake derivatives command later on.) |
|
|
image_thumb | Relation | Mandatory | 1 | Use format: /objects/thumbs/[poster filename]_th.jpg (Note: You need to add this file path here so that these images can be generated using rake derivatives command later on.) |
|
|
image_alt_text | Description | Optional | 1 | Briefly describe the contents of the capstone posters for better accessibility. This is marked as optional but it will be good to add this information whenever you can. |
|
Legend
1
: Only one value is permitted.0..1
: Zero or one value allowed (optional).1..n
: At least one value is required, with no upper limit.0..n
: Any number of values, including none.