"Diethelm Guallar, Gonzalo" wrote:
> > Default schema of TURBINE_USER table contains the minimal
> > subset of user information that is useful to the widest
> > range of applications possible.
> >
> > The following fields are included:
> >
> > first name
> > last name
> > email address
>
> Of course, there is an integer "id" field, right?
> I would get rid of the email address, since it might not be
> minimal enough... [see below].
>
I posted in another thread, but I comment here also. If the integer "id"
is accepted in the "required" schema, it should be available from the User
interface. Currently it is not, and that obliges us to cast User to
TurbineUser.
I would say that this minimalistic schema should always be available from
the User.java interface, as it is the core information and it is
guaranteed that every Turbine user implementation will provide these
fields.
>
> > If application needs to process more information about
> > an user the following actions can be performed
>
> [snip]
>
> This looks good to me.
>
> > Here is the update XML schema of the db. Note that some field
> > names were changed to be more consistent/prettier.
>
> * Should we hear the comments from that guy about Informix, and
> use TB, TRB or TRBN as a prefix (object name lengths) instead
> of TURBINE?
>
> * Why do you define indexes that are identical to the primary key
> definitions? Shouldn't this be handled internally by the DB?
>
> * From looking at the current fields in TURBINE_USER, I think the
> minimum fields should be:
>
> user_id
> created
> modified
> last_login
> objectdata
>
> How do you know you will always use a login_name? Or the user's
> first and last name? e-mail may not always be necessary; etc.
> However, the fields mentioned above are necessary for Turbine
> to be able to handle a user.
>
My experience indicates that email is the single most important piece of
user data that we need. I have even used it as a unique index for a user
database. This avoids repetitions better than any other field, leaving you
with a handle that enables contact with the user. In jyve and jetspeed it
is needed to confirm user registration, for example. I think that the
CONTACT field in vCalendar standard is specified as a url, typically
mailto:, just to give another example.
Of course, it could be different for other apps.
>
> --
> Gonzalo A. Diethelm
> [EMAIL PROTECTED]
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
