Back to all discussions

  •   over 12 years ago

Person schema missing useful things?

Hi!

The "Person" schema seems to be missing some things that would be useful. The OpenID Connect list of fields is nice if you're a person, but it doesn't include a bunch of things that would be useful if you're an artist-as-a-practicing-commercial-entity.

An artist working under multiple pseudonyms or as part of multiple collectives is going to need multiple profiles in this format, no matter what, with no way to link them together if they want to.

The custom schema should support a list of "same artist" IDs, if the artist wants you to be able to find their other personas.

It should support a list of social network URLs, separate from the main "website". Perhaps this can be the same sort of list for artwork-specific SN URLs I suggested in another post.

It should support identifying a preferred form of contact, independent of what might be the artist's personal information in their OpenID profile. Artists represented by galleries, agents, or agencies will need to be able to provide that information. Artists who only want to be contacted via email, or only in person during the event (with no ability to contact them after), should also have those preferences supported.

Thanks,
Vitorio

  • 1 comment

  • Manager   •   over 12 years ago

    Good comments...

    1) Right now there is a 1:1 relationship between artist:person. An artist may have different works at different venues, and can be associated with multiple venues. Introducing the idea that an artist has multiple profiles is too complicated right now. v2?

    2) I added another field to the Person Entity called 'social_urls'.

    3) I also added another field to the Person Entity called preferred_contact so some notes can be entered about the best way to reach the person. Note, the person can manage their profile on the site. The claims from the OpenID Connect Provider will not be used. In many cases, the OpenID Connect provider will not even have the user claims. We just don't want to store passwords on the website... that's a liability.

Comments are closed.