esmé cowles
esmé cowles
@ramachandranv Yes, you can configure a server directory as a source of files in Browse Everything, here's an example of the configuration for that: https://github.com/pulibrary/figgy/blob/master/config/browse_everything_providers.yml#L6-L7
👍 to adding support for content negotiation. I think the RDF and HTML are different formats of the same information, and the fact that the RDF subject URI is the...
There is a branch that does this (creating the hierarchy internally but hiding it): https://github.com/fcrepo4/fcrepo4/tree/hierarchy But there are a lot of places in the fcrepo4 code that assume a 1-to-1...
@jcoyne I completely understand. We've filed a Modeshape bug (https://issues.jboss.org/browse/MODE-2109) and it's actively being worked. It's target at the next release (beta1). Hopefully that will resolve this issue and allow...
@atz If you mean you would like to have shorter IDs and not have to deal with the PairTree hierarchy, I think the AppleTree module might be useful: https://gitlab.amherst.edu/acdc/acrepo-apple-trees @awoods...
👍 to adding support for content negotiation. I think the RDF and HTML are different formats of the same information, and the fact that the RDF subject URI is the...
The other options that's been discussed is using MARC Relators or similiar properties that define roles as properties (they are defined as subproperties of dc:contributor). The benefit of this approach...
The thinking was that the vast majority of cases can be handled by using creator/painter/performer/etc. predicates, which is in keeping with linked data best practices. In the more complicated cases...
@amberbilley: I'm not sure I understand the interoperability concern. Do you have an example of data in another ontology that you think would be difficult to map?