-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always show the same set of fields per record type #229
Comments
I think you mean when displaying a record in the frontend? |
Yes! Both in the table view and the list view a fixed set of fields should be shown. This should probably be the fields as defined in the record ontology. Currently the table view shows all fields that are present in one or more records, and the detail view only shows the fields that are present in that particular record. In the table view some fields may be hidden by default, but they should always be defined. This is per Jeroen's request, because he wants to be able to annotate fields that are not filled in. |
…229) actually clone, not just shallow copy
@tijmenbaarda in #233 (review):
Do you mean you also want to exclude the only-biographical fields from the hidden-but-available columns in the tabulator view of an only-bibliographical catalog (and vice versa)? Because in that case we need a way to distinguish between only-biographical, only-bibliographical and mixed catalogs. Likewise for collections. Writing this out, I realize this probably isn't worth the effort. We can still do it for the record detail view, of course. |
Based on backbone-collection-transformers.
No description provided.
The text was updated successfully, but these errors were encountered: