Code Table Request - sound

[wellerjes]

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 audio within physical media

Context

Describe why this new value is necessary and existing values are not.

creating new attributes taht can be applicable for cultural collections and archives

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.

The identification of the sound characteristics (absence or presence of sound) of audiovisual materials. From the National Archives (https://www.archives.gov/research/catalog/lcdrg/elements/sound.html?_ga=2.72693715.1170924066.1715371360-1651949987.1715371359)

Proposed Definition

Clear, complete, non-collection-type-specific functional definition of the value. Avoid discipline-specific terminology if possible, include parenthetically if unavoidable.

A resource primarily intended to be heard. Via https://www.dublincore.org/specifications/dublin-core/dcmi-terms/

Collection type

_Some code tables contain collection-type-specific values. collection_cde may be found from https://arctos.database.museum/home.cfm_

AV, ARCH, ES, ART Could be applicable to more collections, such as adding sound recordings of bird calls, etc.

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-text

Controlled values

silent - Audiovisual materials recorded without sound.

silent and sound - Audiovisual materials partially recorded with sound and partially recorded without sound. If needed record the primary recording (sound or silent) in attribute method.

sound - Audiovisual materials recorded with sound.

Attribute 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/a

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.

Examples include a music playback file format, an audio compact disc, and recorded speech or sounds. For CHAS:AV, we want to record if the film has audio or is silent

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.

• [ ] 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

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._

• [x] Code Table Administrator[1] - check and initial, comment, or thumbs-up to indicate that the request complies with the how-to documentation and has your approval
• [x] Code Table Administrator[2] - check and initial, comment, or thumbs-up to indicate that the request complies with the how-to documentation and has your approval
• [ ] DBA - The request is functionally acceptable. The term is not a functional duplicate, and is compatible with existing data and code.
• [ ] DBA - Appropriate code or handlers are in place as necessary. (ID_References, Media Relationships, Encumbrances, etc. require particular attention)

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.

1. Can a suitable solution be found here? If not, proceed to (2)
2. Can a suitable solution be found by Code Table Committee discussion? If not, proceed to (3)
3. Take the discussion to a monthly Arctos Working Group meeting for final resolution.

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.

1. Adding an existing term to additional collection types may proceed immediately and without discussion, but doing so may also subject users to future cleanup efforts. If time allows, please review the term and definition as part of this step.
2. The Committee may grant special access on particular tables to particular users. This should be exercised with great caution only after several smooth test cases, and generally limited to "taxonomy-like" data such as International Commission on Stratigraphy terminology.

[Jegelewicz]

What would go in the value for this?

If the thing you are cataloging is a sound recording, then the identification should make that clear - not sure this is needed?

https://arctos.database.museum/name/Sound

[Jegelewicz]

film has audio or is silent

Ah , OK

I suggest instead

sound type - The identification of the sound characteristics (absence or presence of sound) of audiovisual materials. from https://www.archives.gov/research/catalog/lcdrg/elements/sound.html?_ga=2.72693715.1170924066.1715371360-1651949987.1715371359

Your values should come from the authority - https://www.archives.gov/research/catalog/lcdrg/authority_lists/soundlist.html

Silent scope note: Use for audiovisual materials recorded without sound.

Silent and Sound scope note: Use for audiovisual materials partially recorded with sound and partially recorded without sound. The bulk of the materials should be silent.

Sound scope note: Use for audiovisual materials recorded with sound.

Sound and Silent scope note: Use for audiovisual materials partially recorded with sound and partially recorded without sound. The bulk of the materials should be sound.

[wellerjes]

Agree with these definitions and values.

[Jegelewicz]

@ArctosDB/arctos-code-table-administrators decided to avoid the redundancy of

Silent and Sound scope note: Use for audiovisual materials partially recorded with sound and partially recorded without sound. The bulk of the materials should be silent.

Sound and Silent scope note: Use for audiovisual materials partially recorded with sound and partially recorded without sound. The bulk of the materials should be sound.

in favor of

Silent and Sound Audiovisual materials partially recorded with sound and partially recorded without sound. If needed record the primary recording (sound or silent) in attribute method.

to cover both options.

[wellerjes]

Works for me!

[Nicole-Ridgwell-NMMNHS]

box checked.

[dustymc]

I believe this needs a new code table, which will specifications.

Discussions of the values will need Issues.

Possibly something akin to https://github.com/ArctosDB/arctos/issues/7364 would be better; a big-picture overview of these seemingly-related issues would be VERY useful.

[wellerjes]

I believe this needs a new code table, which will specifications.

Outside of https://arctos.database.museum/info/ctDocumentation.cfm?table=ctattribute_type? What should I submit?

[Jegelewicz]

I believe this needs a new code table, which will specifications.

Suggested Code table structure for controlled vocabulary

Term	Description	Search Terms	Documentation URL	Issue URL
Sound	scope note: Use for audiovisual materials recorded with sound.	https://www.archives.gov/research/catalog/lcdrg/authority_lists/soundlist.html	xxxx

[Jegelewicz]

@wellerjes @droberts49 won't this be covered by selection of the appropriate format?

https://www.archives.gov/research/catalog/lcdrg/authority_lists/formatlist.html

for example: Film: INSK - scope note: Internegative, Silent, Color

and maybe you will need to select more than one format per film?

[wellerjes]

Yes, we are okay with selecting more than one format per film.

[wellerjes]

@dustymc do you need any additional information from us to proceed?

[dustymc]

See https://github.com/ArctosDB/arctos/issues/7782#issuecomment-2179342451 - it was agreed that this is redundant with format and should not proceed.