Property | Source | Mod | Description |
|---|
Name | Registry, Can override | Yes | Brief, human-readable description of this format, for listing it in menus.
Used to be "short description". |
Description | Registry, Can override | Yes | Detailed human-readable explanation of the format including its unique aspects. |
Identifier | Registry | No | List of all namespaced identifiers linking this BSF to an entry in an
established data format registry. A BSF must have at least one identifier.
This list is ordered; the first member names the external registry entry
that was originally imported to create this BSF. |
Support-level | User-entered | Yes | Encoding of the local DSpace archive's policy regarding preservation of Bitstreams encoded in this format. Value must be one of: - Unset - Policy not yet initialized, flags format entries that need attention from the DSpace administrator.
- Unrecognized - Format cannot be identified.
- Known - Format was identified but preservation services are not promised.
- Supported - Bitstream will be preserved.
|
MIME-type | Registry, Can override | Yes | Canonical MIME type (Internet data type) that describes this format. This is where the Content-Type header's value comes from, when delivering a Bitstream by HTTP. |
Extension | Registry, Can override | Yes | The canonical filename extension to apply to unnamed Bitstreams when
delivering content over HTTP and in DIPs. (NOTE: Some format
registries have a list of filename extensions is, used to help
identify formats, but we only need the canonical extension in the BSF model. |
LastUpdated | System | No | Timestamp when this BSF was imported or last updated from its home registry. |