-
Notifications
You must be signed in to change notification settings - Fork 1
Storing Person Information via Vdc::Person Objects
jkim-ru edited this page Nov 20, 2017
·
1 revision
Based on the following commit: 613da18500ed9d24170f190d37b17c3001bb16d9
We were looking to customize our VDC application to store and administer registered user information in the underlying Fedora repository.
- Store information on a "person" (aka a
User
) in Fedora if they've registered and been approved to use our Hyrax-based application.- Created the
Vdc::Person
object (person.rb)
- Created the
- Augmented the existing
User
model (user.rb), also used by the Devise gem, to store registration information and an approval flag. - Allow users to register and have their information stored in the
user
db table, but only an approval by an Administrator will create aVdc::Person
in Fedora and give a user the ability to log in. - Use information from a
Vdc::Person
to and from our Works as links within Fedora.- The vanilla Hyrax (1.0.4) application defined creator metadata as a string. However, for this application, we wanted to replace that with a pointer to a
Vdc::Person
object. - We modified the work form so that our "creator" field is populated by a drop down generated from a Blacklight query. We've gotten feedback to try using QA to work with this instead... but that's not how it is now.
- Form drop down - app/views/records/edit_fields/_vdc_creator.html.erb
- Concern that was included in the collection_form.rb and resource_form.rb - app/forms/concerns/vdc/vdc_creator_for_select.rb
- We modified the work indexer and catalog search builder so that Person information (like their name) could produce hits on associated works: https://github.com/dibbs-vdc/ccql/issues/37
- The vanilla Hyrax (1.0.4) application defined creator metadata as a string. However, for this application, we wanted to replace that with a pointer to a
- Eventually create workflows to allow administrators to approve user requests to update a Person's information (for example, if a Person changes his or her email after moving to a different university). This would update the Person's information in Fedora (and anything linked to it). This extra step will be to make sure changes go through an authorized source, much like approval when initially registering.
- If we do get this working eventually, we'll put back the ability to for users to edit their own profile. We disabled the ability for users to edit their profiles. Only Administrators can edit a user's registration and sync with Fedora.
- Eventually set up an external triple store to mirror the Fedora data and be used for other purposes.
Related links: