One thing I see that I thought but forgot to say is that there is a
difference between what DSpace should *present* and what it should
*store*.  For example, it's reasonable to present useful contact
information together with the information that DSpace stores and is
authoritative for: documents and their bound metadata.  Binding the
document to the author is one of the things we do.  But we don't
*use* e.g. telephone numbers, so why store them if we don't have to?  And
we certainly should NOT copy data from the directory (when there is
one) and keep local duplicates which eventually go stale and mislead
our users.  We don't need two sets of stewards for the same data.

What DSpace needs to store, w.r.t. identity, is:

1.  a unique key to represent an identity to a given provider;
2.  a selector for the identity provider.

But we can present a lot more than that, freshly retrieved from
authoritative sources, if we wish to.  We could go query the identity
provider for such details, but we could also just present a link to
the identity service (perhaps configured for direct access to the
individual's record) or reserve an area on the page for the service to
supply a vignette of the user's biographical data and any links it
wants to include.

A local identity provider (such as the password-based provider) can
store and supply incidental identity data, but those data should be
part of the provider and not of the DSpace core.

-- 
Mark H. Wood, Lead System Programmer   [email protected]
Friends don't let friends publish revisable-form documents.

Attachment: pgp2i7USKygYi.pgp
Description: PGP signature

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Dspace-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-general

Reply via email to