Support "value known" annotation

mih commented

2025-04-23 19:26:13 +00:00

Owner

We know we want to export records from the actual knowledge base to the simplesubmit data base, to aid linkage to known things.Typically, we will not want to export all information for that, just enough to allow for identifying the correct item to link.

This can make some instances look underspecified and cause people to invest effort to fill in missing values.

We should be able to express the fact that a particular slot has a known value, but that it is not available to show.

This would be an instance level annotation, where the vakue could be the name of the slot.

We know we want to export records from the actual knowledge base to the simplesubmit data base, to aid linkage to known things.Typically, we will not want to export all information for that, just enough to allow for identifying the correct item to link. This can make some instances look underspecified and cause people to invest effort to fill in missing values. We should be able to express the fact that a particular slot has a known value, but that it is not available to show. This would be an instance level annotation, where the vakue could be the name of the slot.

jsheunis commented

2025-04-24 09:08:34 +00:00

Owner

Could you perhaps share a concrete example, and how that translates to what needs to be done in shacl-vue to achieve this functionality. It is not currently clear to me.

Could you perhaps share a concrete example, and how that translates to what needs to be done in `shacl-vue` to achieve this functionality. It is not currently clear to me.

mih commented

2025-05-06 12:34:09 +00:00

Author

Owner

A Person record comes in via a specific admin application. A filtered Person record (still using the same data model) is loaded into a different application to facilitate linking to this Person record, but without exposing all known information.

This would make the record look incomplete, and a user that cares could feel compelled to enter already known information again. This would be wasteful.

OTOH, we do not want to prohibit providing additional information, for example when something has changed, and the user knows that.

I was thinking that some kind of indicator would help that communicates "Don't worry that this field is empty, we actually have something on record. But if you feel like this particular information needs an update, please go ahead and enter it."

A Person record comes in via a specific admin application. A filtered Person record (still using the same data model) is loaded into a different application to facilitate linking to this Person record, but without exposing all known information. This would make the record look incomplete, and a user that cares could feel compelled to enter already known information again. This would be wasteful. OTOH, we do not want to prohibit providing additional information, for example when something has changed, and the user knows that. I was thinking that some kind of indicator would help that communicates "Don't worry that this field is empty, we actually have something on record. But if you feel like this particular information needs an update, please go ahead and enter it."

jsheunis commented

2025-05-19 11:32:54 +00:00

Owner

Thanks for the example and explanation, I understand now. @mih do you think this is still relevant or necessary, given our more recent approach of having mutliple dumpthings servers, with different levels of annotation, feeding the same shacl-vue instance?

Rows
Columns

Support "value known" annotation #16