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.

Sign up for GitHub

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

Jump to bottom

ActiveFedora::Associations::IndirectlyContainsAssociation should be restructured into two child classes #1332

Open
jrgriffiniii opened this issue Aug 14, 2018 · 0 comments
Open

ActiveFedora::Associations::IndirectlyContainsAssociation should be restructured into two child classes #1332

jrgriffiniii opened this issue Aug 14, 2018 · 0 comments

Comments

@jrgriffiniii
Copy link
Contributor

Two possible LDP Container predicates may be used for this case,
has_member_relation and is_member_of_relation:

https://github.com/samvera/active_fedora/blob/master/lib/active_fedora/associations/indirectly_contains_association.rb#L37

These are currently accessible using either the RDF::Vocab::LDP.contains (https://github.com/ruby-rdf/rdf-vocab/blob/master/lib/rdf/vocab/ldp.rb#L106) or RDF::Vocab::LDP.hasMemberRelation (https://github.com/ruby-rdf/rdf-vocab/blob/master/lib/rdf/vocab/ldp.rb#L114). However, it may be best to explore restructuring these as child classes derived from IndirectlyContainsAssociation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Samvera Component Maintenance
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jrgriffiniii