Page History

...

...

• dspace:submitter – ePerson resource of original submitter of this item.
• dspace:owning_collection – persistent identifier (handle) of Collection that owns this item.
• dspace:license – contents of license bitstream for this item, in a `<bitstream>` tag bitstream_xml (see below).
• dspace:cc_license_text – text of Creative Commons license bitstream for this item, in a `<bitstream>` tag bitstream_xml (see below).
• dspace:cc_license_rdf – RDF of Creative Commons license bitstream for this item, in a `<bitstream>` tag bitstream_xml (see below).
• dspace:cc_license_url – URL of Creative Commons license for this item.
• DAV:getlastmodified – This DAV property is assigned the DSpace last-modified date.
• dspace:handle – the persistent identifier of this resource in URN format, e.g. `hdl:123.45/6789`.
• dspace:withdrawn – `true` or `false`, indicating whether the Item has been withdrawn. This is the only property most users will have permission to read on a withdrawn Item.

Bitstream objects::

• Wiki Markup{{DAV:getcontentlength}} -- value returned by bitstream's {{\[get Size\]}} – value returned by bitstream's getSize().
• DAV:getcontenttype – mimetype from bistream's format.
• NOTE: the DSpace object model has no notion of `getcontentlength` for Bitstreams, so we cannot offer it.
• dspace:source – bitstream's source attribute.
• dspace:description – bitstream's description attribute.unmigrated-wiki-markup
• {{dspace:format}} -- – bitstream's {{\[get Format\]getFormat().getID()}}. Wiki Markup{{
• dspace:format_description}} -- – bitstream's {{\[get User Format Description\]}}.

• Wiki Markup
  {{dspace:checksum}} -- bitstream's {{\[get Checksum\]()}}.

• getUserFormatDescription().
• dspace:checksum – bitstream's getChecksum().
• Wiki Markup{{dspace:checksum_algorithm}} -- – bitstream's {{\[get Checksum Algorithm\]getChecksumAlgorithm()}}.unmigrated-wiki-markup{{
• dspace:sequence_id}} -- returned by bitstream's {{\[get Sequence ID\]}} – returned by bitstream's getSequenceID().
• dspace:bundle – name of bundle in which bitstream was created.
• dspace:handle – the persistent identifier of this resource in URN format, e.g. `hdl:123.45/6789` (but usually not available for bitstreams (yet?))

...

• dspace:submitter – EPerson resource of original submitter of this item.
• dspace:collection – persistent identifier (handle) of Collection to which this item is being submitted.
• Wiki Markup{{dspace:has_multiple_files}} -- value of `\[has Multiple Files\]()` – value of hasMultipleFiles()
• Wiki Markup{{dspace:has_multiple_titles}} -- value of `\[has Multiple Titles\]()` – value of hasMultipleTitles()
• Wiki Markup{{dspace:is_published_before}} -- value returned by `\[is Published Before\]()` – value returned by isPublishedBefore()
• Every in-progress item also has one child resource which is a DSpace Item.

...

Model the Bitstream Format registry as one resource of the "collection" type. That top-level resource is just a container for the format records, so they can all be listed (e.g. by `PROPFIND`). The formats themselves are child resources of the Registry, named by the string returned by `get Short DescriptiongetShortDescription()` on the format.

• The Registry URI is _/prefix_/format/
• Each Bitstream Format's URI is _/prefix__/format/_short-description
• `GET` is not implemented on any of these resources.
• `PUT` of a new Bitstream Format URI creates it. The request body must be empty.
• Bitstream Format resources have the following properties. They are all settable unless marked read-only.
  • `DAV:displayname` – same as description
  • `DAV:resourcetype` – empty. (`/format/` is a collection).
  • `dspace:type` – `<bitstream-format/>`
  • `description` – Full description of the bitstream format.
  • `extensions` – Comma-separated list of filename extensions associated with this format.
  • `ID` – READ-ONLY; internal database ID of this format.
  • `MIMEType` – Internet format type, aka MIME type, associated with this format. May not be unique amongst formats.
  • `support Level` – Support level, one of `UNKNOWN`, `KNOWN`, `SUPPORTED`.
  • `is Internal` – Is this format useed to store internal system information, rather than content? One of `TRUE`, `FALSE`.

...