Much of the functionality that is exposed through the RESTful HTTP API is also available using an HTML user interface interpreted by your favorite web browser. Whether your request for particular HTTP API HTTP endpoints results in an HTML UI or more machine-readable formats is based on content negotiation headers. This tour walks you through the major user interface components when accessing the HTTP API through a web browser.
...
From here you can:
- Create new Resources (Containers or Binaries)
- Inspect the properties of Resources.
- Update the properties of Resources.
- Navigate the Repository Hierarchy of Resources.
- Import/Export Resources.
- Start Transactions.
...
The user interface is divided into regions.
- Navigation bar (at the top)
- Resource information and navigation (center left center)
- Optional resource actions (center right center)
Navigation Bar
The navigation bar, which appears at the top of each page, includes links to the following:
Resource Information
...
| Section |
|---|
| Column |
|---|
|
| Column |
|---|
1 Object Title If a title (either http://www.w3.org/2000/01/rdf-schema#label or http://purl.org/dc/elements/1.1/title) is available, it is displayed here. If If no title has been assigned, the resource URI is displayed in this location.
2 Object Path Fedora 4 is different from Fedora 3 in that there is an innate tree hierarchy to the repository rather than a flat structure. The path (list of ancestors) for the viewed resource is presented below the object title. Performance Performance is expected to be better with a deeper hierarchy with fewer items per level as opposed to a shallower shallow hierarchy where each level has a larger number of siblings. The The automatic ID (and path) generated is meant to optimize performance, but you may use your own organizational strategy when creating resources.
In this particular example, the container was created with a fully qualified name including a namespace and local name (separated by a colon). Fedora Fedora 4 does not require (nor recommend) that identifiers have namespaces.
3 Featured PropertiesVery basic metadata such as the UUID and modification/creation times and users are presented below the resource path. 4 Children
Any children that the container has will be listed and linked here. Like Like the parent containter, if these children have a child resource has recognized title metadata, that the title will be presented here rather than their its URI. 5 All Resource Properties All properties of the resource are presented here. Hover Hover your mouse over the namespace prefix to see the full namespace.
6 Other Resources A subset of properties from the parent resource. Click on the grayed gray box to expand the list of properties or the label text to view that resource directly.
|
|
...