Discuss Creator order/ make plans

davidschober commented 7 years ago

Description

As we all know, ordered creators are a problem. As discussed in (#289), there is a desire to have creators ordered arbitrarily. Chris Diaz and I have talked and we are OK pushing it out, but we need a plan to give the proteomics folks. We need to discuss and document possible solutions with proposed timelines.

Possible Solutions

Fill in solution pitches, with timelines and risks.

Done looks like

a proposal or series of proposals is pitched to Diaz and Schober with estimates.

chrisdaaz commented 7 years ago

when this is ready to be scoped, i can see who from the community would be able to help with a solution and push upstream.

https://github.com/samvera/hyrax/issues/1568

kdid commented 7 years ago

Developer discussion scheduled for 9/25/2017

bmquinn commented 7 years ago

Possibility 1: Upstream change. Ordering sub resource binary which would allow properties with an orderable attribute to automatically create an ordered sub resource for the property

Automatically add a sub resource to the model based on an "orderable" attribute.

Current model:

<http://arch.library.northwestern.edu/concern/generic_works/5712m658s> a <http://pcdm.org/models#Object>,
<http://purl.org/dc/elements/1.1/creator> "Michael",
     "Chris",
     "Carrick",
     "Brendan",
     "Karen";

Potential solution:

Store a string in a binary subresource that maintains the order of the fields entered in the form. This subresource would then be automatically overwritten upon updates to the record.

Ordered subresource alongside top-level assertions example:

<http://arch.library.northwestern.edu/concern/generic_works/5712m658s> a <http://pcdm.org/models#Object>,
<http://purl.org/dc/elements/1.1/creator> "Michael",
     "Chris",
     "Carrick",
     "Brendan",
     "Karen";
<http://nufiaweb-s.library.northwestern.edu/concern/generic_works/7h149p90s/http_purl_org_dc_elements_1_1_creator_order> "Michael\nCarrick\nBrendan\nKaren\n";

Upsides:

No additional data modeling necessary. Does not create unnecessary predicate
Works in the background with no user intervention required (e.g. combining creator names manually in a semicolon-separated string in another property like OrderedCreator)

Downsides:

It's not a good time to be adding complex functionality to ActiveFedora since the upcoming Hyrax-Valkyrization sprint is aiming to remove ActiveFedora altogether. It is not clear if this solution will make sense in the upcoming Valkyrized Hyrax.
There is not a clear path for migrating this data. It's just a string stored without external references like URI's so would not be simple to migrate in the future (i.e. you break apart the string by newlines and then do what with that data?)

kdid commented 7 years ago

Possibility 2: Short Term Workaround Locally.

Add a "Main Creator" or "Primary Creator" property to our Generic Work model that contains the main creator with a different predicate.

Upsides:

Faster, doesn't depend on waiting for upstream changes

Downsides:

Would have to choose a different predicate than dc:creator for one or the other
Would need to fix existing data, probably manually
Doesn't deal with multiple main creators
Facets would need to be addressed.
Not a global solution. Wouldn't work for different fields.
Data would have to be remigrated when a better solution is found.

jenyoung commented 7 years ago

Don't do Option 2. It will make things supercomplicated from a metadata standpoint. You could just define the Creator field for the 'Primary Creator' and add the rest as Contributors.

chrisdaaz commented 7 years ago

is what PSU did here applicable for us? @bmquinn @kdid

kdid commented 7 years ago

@cpd3149 - we did talk about that option but in general felt that increases the complexity of our customizations so much that we would be very far from core Hyrax and our customizations would be hard to maintain. (Note that I don't think PSU is using Hyrax.)

We see that there has been some discussion of putting this approach in Hyrax. Don't see notes of the special call that was mentioned here to discuss it:

https://wiki.duraspace.org/display/samvera/Samvera+Tech+Call+2017-08-02

And there is also reference to the special call to discuss it here but don't see notes from it.

https://groups.google.com/forum/#!searchin/samvera-tech/person$20model$20object$20in$20fedora$20rutgers%7Csort:relevance/samvera-tech/TZj8HN7Rkd4/FxNCY37yAgAJ

Do you know the outcome of the discussions about putting this in Hyrax?

Note that it also doesn't solve the ordering problem for other fields. (We don't want to go down the road of creating models for Keywords, titles, etc)

chrisdaaz commented 7 years ago

it doesn't seem like there's anything we can do. putting this on hold.

nulib / arch