%@page language="java"%> <%@page contentType="text/html; charset=UTF-8" %> <%@page import="org.dataone.client.v1.itk.D1Client"%> <%@page import="org.dataone.service.types.v1.SubjectList"%> <%@page import="org.dataone.service.types.v1.Person"%> <%@ include file="setup.jsp"%>
Please enter biographical details for this identity. Your identity provider may have provided some of the information, depending on that institution's policy. You are free to edit this information to keep our records current.
Equivalent identities allow us to maintain continuity in our access control rules as institutional affiliations shift over time. A new identity can be "mapped" to an older identity so that the new identity is granted the same access privileges as the older identity; and vice versa.
Identity mapping is a 2-step process: a request by Identity A to map as Identity B must be confirmed by Identity B. Pending requests for you that were initiated by other accounts are below.
You may request that your current identity be mapped to one below. A request must be confirmed by the other identity before it is active.
Groups allow us to define access control rules for one identity (the group) that apply to all the members.
The account that created the group can add and remove members from it. Eventually, we will define rules that allow other accounts to edit the group.
New account details should be verified by an administrator before they become active in DataONE. This is particularly true of Google and ProtectNetwork identities that provide no assurances that someone is who they claim to be. Accounts from institutions with which DataONE has an established trust relationship may not require verification.