+1
Requested

Key differences in fieldviews for content type video vs. record

Ardath 6 months ago in ADAM Core • updated by petra.tant 3 months ago 5

Toyota is using approx. 130 fields for their records and they are categorizing these fields in different panels by updating the necessary items in the .assetStudioRecordFieldView-setting.

UX meta-data fields

What is the use case you want to solve? Can you provide some more input?

Joris will need to provide more input.  Please forward to him.  I am not sure how to do that in this system.

From SNOW:
Description: Toyota is using approx. 130 fields for their records and they are categorizing these fields in different panels by updating the necessary items in the .assetStudioRecordFieldView-setting.
However, this setting is not used for records with ContentType video (also see screenshots attached). Because of this Toyota has chosen not to use ContentType video at all for the moment.

My suggestion
- for a long term solution: make sure that the Video view uses the .assetStudioRecordFieldView-setting instead of dumping all fields in an "Other Fields"-panel.
- for a short term solution (TOYOTA): make sure that we *can* replace the view and edit links (incl. clicking the title) in the mosaic/preview view with the /EditAsRecord and /ViewAsRecord (that last one doesn't exist yet i think).

Business Use Case:

If I'm readying this post correctly, we've run up against the same thing. Our photos use a field view that return the fields by field group, and then allow us to narrow to a specific field group if desired. With the videos, we were able to set it up so that we can get the fields to show up by field group, but we can't do the same narrowing if desired. We've also found in this view for videos that each field group is automatically closed, requiring the user to click into it before seeing any information, whereas with our photos they're automatically open. 


It brings up a concern for us that our users aren't going to take the effort to see usage restrictions, or even be aware that they might exist.


It would be really nice if the right side "record" information could behave the same way for both content types.