You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have two types of serialization. One for person and one for organizations. They should be consistent.
Both dropdown options should display the same information (e.g. one has icons, the other doesn't, one has acronyms inside parenthesis while the other does it underneath the name).
There is no way to differentiate two affiliations with the same name (like Heidelberg University and Heidelberg University), the only differentiation is the ROR id which is not that useful for the end user (more on this on the data model concerns)
The affiliations accordion in the record's landing page does not show both affiliations if they have the same. It's a bit of an edge case. Anyway, this happens because the UI serializer (backend) aggregates the affiliations by name instead of id.
Concerning the data dump
We need to enrich the information we have on affiliations so we can clearly differentiate two affiliations. Each name + location seems like a good candidate.
I'm going to be doing some of the same ROR enhancements for the funders field, which has a lot of the same issues. I think our ROR handling can be harmonized-let me know if you're going to start working on this so we can coordinate.
UI inconsistencies
person
and one for organizations. They should be consistent.ROR id
which is not that useful for the end user (more on this on the data model concerns)Concerning the data dump
See: https://ror.readme.io/docs/create-ror-powered-typeaheads
The text was updated successfully, but these errors were encountered: