You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2021. It is now read-only.
(Using the latest code from Git)
When a property has too many values it is displayed this way in the HTML :
ore:aggregates [57 values]
However I would expect all the values (57 in this case) to be present in the RDF returned from the RDF view. But they are not. How is an application consuming this RDF supposed to know that these 57 values are to be fetched at some other URL ?
Is there a way to desactivate this behavior that hides the list of values when it is too long ? if yes would it make them appear in the RDF ?
Cheers
The text was updated successfully, but these errors were encountered:
This is currently broken in various ways. As a workaround, you can increase HIGH_DEGREE_CUTOFF to something really large in ResourceDescription.java and recompile. This effectively turns the feature off.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
(Using the latest code from Git)
When a property has too many values it is displayed this way in the HTML :
ore:aggregates [57 values]
However I would expect all the values (57 in this case) to be present in the RDF returned from the RDF view. But they are not. How is an application consuming this RDF supposed to know that these 57 values are to be fetched at some other URL ?
Is there a way to desactivate this behavior that hides the list of values when it is too long ? if yes would it make them appear in the RDF ?
Cheers
The text was updated successfully, but these errors were encountered: