Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance the history database: record at the triple level #183

Closed
jmvanel opened this issue Oct 18, 2017 · 1 comment
Closed

Enhance the history database: record at the triple level #183

jmvanel opened this issue Oct 18, 2017 · 1 comment

Comments

@jmvanel
Copy link
Owner

jmvanel commented Oct 18, 2017

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.

jmvanel added a commit that referenced this issue Nov 21, 2017
…level" #183

New function getMetadataAboutTriple() ; it seems that the history database actually records metadata (user, timestamp) at the triple level
@jmvanel
Copy link
Owner Author

jmvanel commented Nov 26, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant