Repository navigation
Services
These services are generally confined to RCM and will not be publicly accessible.
Until there is a more universal Rerum User module, the RCM tools will authenticate based on an internal user/pass combo, creating an Agent for each user.
The Collection itself will be recorded externally in RERUM, but the preferences for layout, type, and public status will be local to the application.
Other Agents who have roles related to the editing of this Collection and their relative positions.
Turn specific tools on and off for describing different types of collections.
These services are core to RCM, but are not a built-in part of RCM.
As Rerum User module is created, it will replace the local instance here, a sort of SSO within the Rerum ecosystem.
For any new type of entity, RCM may request a permanent URI from RERUM or other configured service.
For new Users, Applications, or other Agents within the RCM application, a permanent URI may be created from RERUM or other configured service.
All description, assertions, commentary, and containers around RCM resources will be stored in RERUM or similar configured service.
Linked Data Notifications related to important events or qualities of Collections may be pushed to Rerum Inbox or other configured service.
These comprise interfaces or services that will be used unmodified with existing outputs from RCM or RERUM.
Analysis or representation of word count, concordances, geographic locations, etc. may be produced from the Collection objects.
Universal Viewer, Mirador, and other simple interfaces that require only a Collection or Manifest to produce a rendering of an object may be linked out to or instantiated inside the application environment.