Login

Knowing a User is important, but the authentication system is not. A user may save their identity in localStorage to avoid "finding" themselves again. An unknown user will need to authenticate and then only proceed if a public Agent is tied to their user.

1. Search Public Agents in RERUM for mbox/name/etc.
2. Paste a UUID/URI from anywhere to use.
3. Import an identity from a supported site (e.g., Orchid)

Once User is connected to Agent, the creator for new data will be the public agent. Agent+RCM Agent as _rerum.generator will authenticate the contributions.

*NB: Nothing should be created without an authentic creator attributed.

localStorage

As simple key-value pairs, login information should be easy to store in localStorage, while more complex items may be put into InnoDB.

localStorage.set("creator","http://store.rerum.io/v1/id/Agent-01")

The Agent can be resolved with a filter for Agent+RCM Agent as _rerum.generator to find all the updates that a user may have made to their account.

{
  "@id": "http://store.rerum.io/v1/id/Agent-01",
  "@context": "http://store.rerum.io/v1/context.json",
  "name": "Angela Userton",
  "givenName": "Angela",
  "familyName": "Userton",
  "mbox": "email@compuserve.net",
  "sameAs": "https://orcid.org/0000-0001-2345-6789"
}

User Customization

The User should know whether they are editing their private preferences or their public profile at all times. A different area of the form and reminder text must always be included.

Public Profile

• update Display, Given, Family, Alternate Names
• add mailboxes, homepages
• link other authoritative URIs
• see annotations made by others
• link digital publications

Private Profile

This will not be as important and can be stored only in the localStorage as a way of keeping it secure.

• Layout preferences
• Theme, dark/light mode
• Timezone adjustment
• local display name
• trusted others filters