Some RIF-CS keys hold the full URL value starting with http:// or https://. This can cause problems in the graph inference engine in regards to graph key. The key is expected to be a valid URI and traditionally built using local_id as follows
researchgrapg.org/{namespace}/{local_id}
so for an ANDS record with local_id=http://nla.gov.au/nla.party-542098 the key is assembled as researchgraph.org/ands/http://nla.gov.au/nla.party-542098.
The recommended methods to fix this issues are:
Option 1: Use RDA Record ID for the value of local_id such as "561690" instead of "http://nla.gov.au/nla.party-542098". The result will be
-- key = researchgraph.org/ands/561690
-- local_Id = 561690
Option 2: Keep the RIF-CS key for local_id and use the RDA Record ID for assembling the graph key. The result will be
-- key = researchgraph.org/ands/561690
-- local_Id = http://nla.gov.au/nla.party-542098
I think option 2 is preferable as it enables easily tracing the graph nodes to RIF-CS content, and also avoid the loss of data when we do not capture the RIF-CS key in any other node property.
Some RIF-CS keys hold the full URL value starting with
http://orhttps://. This can cause problems in the graph inference engine in regards to graph key. The key is expected to be a valid URI and traditionally built using local_id as followsresearchgrapg.org/{namespace}/{local_id}so for an ANDS record with
local_id=http://nla.gov.au/nla.party-542098the key is assembled asresearchgraph.org/ands/http://nla.gov.au/nla.party-542098.The recommended methods to fix this issues are:
local_idsuch as "561690" instead of "http://nla.gov.au/nla.party-542098". The result will be -- key = researchgraph.org/ands/561690 -- local_Id = 561690I think option 2 is preferable as it enables easily tracing the graph nodes to RIF-CS content, and also avoid the loss of data when we do not capture the RIF-CS key in any other node property.