Open jamsden opened 4 years ago
Just to get started, I have now changed toString() to be "identifier (shortTitle)". Identifier is always there. ShortTitle is somethere there. So at least we have something to show to start with.
BUT, I just realised that unless we create and store Links (a reified resource) instead of URIs, it will not be possible to display the label, instead of hte URI. Alternatively, I need to do a GET on each property of a resource, in order to be able to display it.
Is it worth it?
Jad, I would prefer title | identifier, never both - that is prefer title if it exists, otherwise use identifier. This keep the UI logical and clean unless the information isn't available.
Sure. It can be easily changed now that I have a system in place. I guess you mean “shortTitle” instead of title. And also note that shortTitle doesn’t exist in the source. I had to add it from another property.
So, I can now show something other than the URIs on the query page.
Once we have more relevant content (currently only identifier seems to have a value), I will update the toString() to be shortTitle.
I happened to just push a change to master. Based on what's being deployed, let's see what more we need to do on this issue.
You can code for shortTitle and if its not there use identifier.
Project should be its title for example.