Jegelewicz
commented
2 months ago The DCMI link should be http://purl.org/dc/terms/format
Recommended practice is to use a controlled vocabulary where available. For example, for file formats one could use the list of Internet Media Types [MIME]. Examples of dimensions include size and duration.
| What | How |
|---|---|
| Definition: | The format of the media comprising the audiovisual materials. For example, the format of videotape can be VHS or Betamax, the format for sound recordings can be Master or Stamper Matrix, or the format for motion pictures can be Duplicate Negative Composite or Master Projection Print Composite. |
| Purpose: | Provides information on the media format useful for reproduction, storage, equipment selection, and playback. |
| Relationship: | This element is dependent on Media Type. Each media occurrence of the archival materials must have a media type specified to create Format. |
| Guidance: | Choose the correct term from the Format Authority List. |
With an actual list of authorities...
wellerjes
droberts49
Nicole-Ridgwell-NMMNHS
dustymc
Initial Request
Goal
Describe what you're trying to accomplish. This is the only necessary step to start this process. The Committee is available to assist with all other steps. Please clearly indicate any uncertainty or desired guidance if you proceed beyond this step.
create an attribute to record physical media
Context
Describe why this new value is necessary and existing values are not.
creating new attributes that can be applicable for cultural collections and archives format is different from materials; for example: materials: nitrate film; format: 35mm
Table
Code Tables are http://arctos.database.museum/info/ctDocumentation.cfm. Link to the specific table or value. This may involve multiple tables and will control datatype for Attributes. OtherID requests require BaseURL (and example) or explanation. Please ask for assistance if unsure.
https://arctos.database.museum/info/ctDocumentation.cfm?table=ctattribute_type
Proposed Value
Proposed new value. This should be clear and compatible with similar values in the relevant table and across Arctos.
format
Proposed Definition
Clear, complete, non-collection-type-specific functional definition of the value. Avoid discipline-specific terminology if possible, include parenthetically if unavoidable.
The file format format, physical medium, or dimensions of the resource. http://purl.org/dc/terms/format
Via https://www.dublincore.org/specifications/dublin-core/dcmi-terms/Collection type
_Some code tables contain collection-type-specific values.
collection_cdemay be found from https://arctos.database.museum/home.cfm_AV, ARCH, EH, Art
Attribute Extras
Attribute data type
If the request is for an attribute, what values will be allowed? free-text, categorical, or number+units depending upon the attribute (TBA)
free-textcontrolled vocabularyAttribute controlled values
If the values are categorical (to be controlled by a code table), add a link to the appropriate code table. If a new table or set of values is needed, please elaborate.
n/aFormat Authority List
Attribute units
if numerical values should be accompanied by units, provide a link to the appropriate units table.
n/a
Part preservation attribute affect on "tissueness"
if a new part preservation is requested, please add the affect it would have on "tissueness": No Influence, Allows, or Denies
n/a
Priority
Please describe the urgency and/or choose a priority-label to the right. You should expect a response within two working days, and may utilize Arctos Contacts if you feel response is lacking.
Example Data
Requests with clarifying sample data are generally much easier to understand and prioritize. Please attach or link to any representative data, in any form or format, which might help clarify the request.
I have an example, but it is encumbered; please let me know if you need me to change permissions to view it: https://arctos.database.museum/guid/CHAS:AV:MF-0033
Available for Public View
Most data are by default publicly available. Describe any necessary access restrictions.
n/a
Helpful Actions
[x] Add the issue to the Code Table Management Project.
[x] Please reach out to anyone who might be affected by this change. Leave a comment or add this to the Committee agenda if you believe more focused conversation is necessary.
@ArctosDB/arctos-code-table-administrators @mkoo
Approval
All of the following must be checked before this may proceed.
_The How-To Document should be followed. Pay particular attention to terminology (with emphasis on consistency) and documentation (with emphasis on functionality). No person should act in multiple roles; the submitter cannot also serve as a Code Table Administrator, for example._
Rejection
If you believe this request should not proceed, explain why here. Suggest any changes that would make the change acceptable, alternate (usually existing) paths to the same goals, etc.
Implementation
Once all of the Approval Checklist is appropriately checked and there are no Rejection comments, or in special circumstances by decree of the Arctos Working Group, the change may be made.
[ ] Review everything one last time. Ensure the How-To has been followed. Ensure all checks have been made by appropriate personnel.
[ ] Add or revise the code table term/definition as described above. Ensure the URL of this Issue is included in the definition. URLs should be included as text, separated by spaced pipes. Do not include HTML in definitions.
Close this Issue.
DO NOT modify Arctos Authorities in any way before all points in this Issue have been fully addressed; data loss may result.
Special Exemptions
In very specific cases and by prior approval of The Committee, the approval process may be skipped, and implementation requirements may be slightly altered. Please note here if you are proceeding under one of these use cases.