Documentation: Design NonRDFResource Entity

[dannylamb]

We need a plan for modeling a Fedora NonRDFResource in Drupal as an entity.

Think in terms of what class to extend and what base fields it would have. What would the annotation look like?

[DiegoPino]

Not a replacement to what we already have as custom entity for this one, but valid exploration needs to be made for https://github.com/drupal-media/media_entity, and in deep.

This module defines a very similar custom entity as we have in https://github.com/DiegoPino/claw-drupal8/blob/master/src/Entity/FedoraResource.php

but it goes further integrating a Plug in system (based on the very cool Drupal 8 Plugin API) that provides specific integrations for images, video, tweets, etc.

See more here https://www.drupal.org/developing/api/8/plugins

This last part allows us to delegate the burden of media management and of "solution packs based on media types" at all.

But: we need to explore how to extend the idea to RDF. We need people @Islandora-CLAW/sprinters to read code and explore what is already there and what we have missing and plan for an strategy that involves as less code as possible, but also robust enough.

E.g. I can think of a way of embedding this media entities (and their "types", see ) into our custom entity nonrdfsource entity. And let our entity just handle the fedora sync, delegating the local storage to media_entity (win, win).

[ruebot]

We need people @Islandora-CLAW/sprinters to read code and explore what is already there and what we have missing and plan for an strategy that involves as less code as possible, but also robust enough.

Sounds like a good priority for the September sprint.

[dannylamb]

Yes, we'll have to look at this more deeply and see just what would be the best way to approach this.

We need to slather just a little bit extra goodness on top of media entity, and I don't know enough yet to say precisely how. Maybe syncing and other stuff could be traits we slap on as needed.

[DiegoPino]

@dannylamb true, I think we need to know more about Drupal 8 and that task needs to be distributed amongst all other sprinters and new people also or it will be a small group only making decisions. I can offer as much support as i can if people have questions (but questions also mean documentation reading) and i feel i'm just scratching the surface. Out of topic maybe.

[dannylamb]

Closing since sprint is over. We can open another ticket to 'revisit' this concept later if required.