Feature #10928
Updated by Costantino Perciante over 7 years ago
**Implemented**:
* similar records cannot be added or removed, "merge" is the only allowed operation;
* similar records can be a lot; this has to be taken into account (scrollable panel);
* the panel should offer the possibility to suggest records to be merged (via UUID for now);
* connections can be suggested (the panel will offer the possibility to add the UUID of a record and to inspect its content);
* annotation message is not mandatory;
**To be implemented**:
* handle merge operation:
* involved records' status is immediately set to "To Be Merged";
* KB will perform immediate updates (e.g. Traceability Flag) by keeping the same "To Be Merged" status;
* there is a 24h window to revert the changes: the link will be sent to GRSF Editors and Reviewers (the link format will be decided ASAP to avoid multiple usages). *The link allows only to ignore merges (other applied changes must be reverted manually)*;
* if no revert is asked, the new merged record will be published (its first status will be *Pending*)(1)
* handle revert after successful merge:
* rejecting operation on a record derived from a merge should do it (again, see note 1)
* about Connections:
* does the KB already suggest some connections? (I hope so)
* Suggested connections can either be accepted ("Connect" takes place) or Removed (thus we need to modify a bit the JSON object and the representation in the catalogue) (see note 2)
* about notifications:
* actions will be notified via mail to the editor who asked the changes as well as the reviewers (see note 3);
* a post with a proper hashtag will be created in the GRSF Admin VRE to keep track of the changes;
1) This should follow: a new grsf record is created and the oldest removed from the catalogue. The reviewers/editors can still recover the old data by rejecting the newly created record. The reject operation should then remove the merged record and republish the original grsf records somehow.
2) The connections field now looks like:
~~~
"connections": [{
"source_knowledge_base_id": "...",
"dest_knowledge_base_id": "...",
"source_domain": "..."
}]
~~~
Something like this may work.
~~~
"connections": [{
"source_knowledge_base_id": "...",
"dest_knowledge_base_id": "...",
"source_domain": "...",
"connect": true/false
"remove" : true/false
}]
~~~
Moreover, we need to change a bit the object accepted by the grsf-publisher. We can turn it into:
~~~
"connected": "similar_grsf_records": [{
"semantic_identifier": "url": "...",
"short_name": "id": "...",
"knowledge_base_id": "description": "...",
"name": "...",
"connected" : true/false
}]
~~~
The "connected" field reflects the status of the "connect" one above. If the admin chooses to "remove" a potential connection then it will disappear from the catalogue page. Hope I got it right.
3) On merge and dissect operations a link is sent to editors/reviewers by which they can ask the knowledge base to ignore the operation (no, it won't be put in a post)
