Skip to content
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

Viewers in CLAW #811

Closed
mjordan opened this issue Mar 3, 2018 · 7 comments
Closed

Viewers in CLAW #811

mjordan opened this issue Mar 3, 2018 · 7 comments

Comments

@mjordan
Copy link
Contributor

mjordan commented Mar 3, 2018

There may have already been some discussion of how we should implement the equivalent of 7.x's solution pack viewers. D8 seems to have a lot of flexibility (well, at least that's the impression I get) around how to render content. Display Suite may be relevant, but the Media Entity module, which we're already using, does too, with "display modes". There are probably other existing frameworks we could look at.

My specific question is has there been any discussion about how we can provide flexibility in how specific Islandora content types (so far, Islandora Image and Islandora Collection) and associated binary media entities (so far, web content, TIFF, and JP2 media) can be presented to users in a modular way? A simple example is the ability to configure and use different video players. For video, it makes sense to use at least as a default whatever the rest of the D8 community is using, but what if that video is also an oral history? Another example is how we will render complex objects like books and newspapers to users.

I'd also like to suggest that we consider Context and its potential to allow site admins to configure how content can be presented to users based on specific, configurable conditions. A real use case that we have at SFU is to have all objects in one collection use a specific 7.x viewer while objects of the same content model in another collection use another viewer. There is a JIRA ticket for this sort of thing in 7.x already.

If having a use case framing this set of questions would be helpful I'd be happy to create one.

@mjordan
Copy link
Contributor Author

mjordan commented Mar 3, 2018

Also like to add that this question might be relevant to porting over 7.x metadata display profiles. D8 already allows configuration of node field-level output, but considering how often metadata display profile are configured and customized in 7.x, we may want to implement them in CLAW from the perspective of how a profile is a reusable aggregation of specific fields. Again, Context might be useful here. The killer reaction for 7.x Context, at least for us, is the ability to have all objects in one collection, regardless of content model, use the same Islandora Solr metadata display profile. We've touched on this already in #799.

@whikloj
Copy link
Member

whikloj commented Mar 5, 2018

Drupal 8 uses Field Formatters which allows you to specify (I think) on a per-field basis which formatter you use. I would suggest that any viewers we create use this setup and then (as you mention) could be altered via Context.

Display Suite appears (to my reading) as an easy way to configure the entire node view. I think this is neat, but I also think it could be an option that users can choose. One of probably many (from simple templating, Views, etc)

https://www.drupal.org/docs/8/creating-custom-modules/create-a-custom-field-formatter

https://github.com/Islandora-CLAW/openseadragon

@mjordan
Copy link
Contributor Author

mjordan commented Mar 5, 2018

Sweet, thanks, I'll take a look.

@mjordan
Copy link
Contributor Author

mjordan commented Mar 7, 2018

Note from March 7, 2018 CLAW call: display modes are configurations defining sets of field formatters.

@Natkeeran
Copy link
Contributor

Recent content modeling overhaul, supporting new viewers has been greatly simplified. In most cases, you don't need to do any coding. Additional notes here: https://github.com/Natkeeran/Notes/blob/master/configure-new-viewer-in-claw.md

@dannylamb
Copy link
Contributor

@mjordan If we took @Natkeeran's notes and put them into our documentation, could we consider this issue/question resolved?

@mjordan
Copy link
Contributor Author

mjordan commented Jul 30, 2018

Yes, I believe so. Feel free to close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants