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
Currently, the metadata (author and timestamp) are not at the triple level, but are attached at the level of the pair subject - predicate.
As a consequence, in muti-value case, all triples for pair subject - predicate are labeled like the last modification, even the triples coming from Internet.
The text was updated successfully, but these errors were encountered:
…level" #183
New function getMetadataAboutTriple() ; it seems that the history database actually records metadata (user, timestamp) at the triple level
Actually the history database actually records metadata (user, timestamp) at the triple level.
The faulty code that confuses all timestamp and user information for a couple (subject, property) is UserTraceability. addUserInfoOnTriples()
where val resultsUser = mutable.Map[String,String]()
should be turned into something like: val resultsUser = mutable.Map[(String,String), String]()
and probably also later change return type of TimeSeries. getMetadataAboutSubject()
to return a List of Map's from (property, object) to (timestamp, user)
which is exactly what callers need.
Currently, the metadata (author and timestamp) are not at the triple level, but are attached at the level of the pair subject - predicate.
As a consequence, in muti-value case, all triples for pair subject - predicate are labeled like the last modification, even the triples coming from Internet.
The text was updated successfully, but these errors were encountered: