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

Integrate legacy e3value functionality #55

Closed
danionita opened this issue Aug 25, 2016 · 8 comments
Closed

Integrate legacy e3value functionality #55

danionita opened this issue Aug 25, 2016 · 8 comments
Labels
Milestone

Comments

@danionita
Copy link
Owner

The following modules need to be broken off the old e3value tool and integrated into the new tool.
Currently waiting for the developers of e3value to provide this code.

@danionita danionita modified the milestones: V1.0, Beta Aug 25, 2016
@bobismijnnaam
Copy link
Collaborator

bobismijnnaam commented Oct 23, 2016

Stuff I had to do before I got a sensible error message:

  • Replaced - with _ (s/-/_/g)
  • Added xml header
  • Added doctype header
  • Did the weird thing with the &'s in the rdf:RDF tag
  • Removed the weird doctype and inlined the urls again (with correct dashes)

@bobismijnnaam
Copy link
Collaborator

Then I added valuations and value transactions and the simple test I implemented generated an excel sheet.

@danionita
Copy link
Owner Author

Do you mean to say that after you did all that, the NCF parsed the RDF
correctly and completely?
Does this mean it is fixed now or was this just a diagnosis?
What is "the weird thing with the &'s in the rdf:RDF tag"?

On Sun, Oct 23, 2016 at 1:33 PM, Bob Rubbens notifications@github.com
wrote:

Then I added valuations and value transactions and the simple test I
implemented generated an excel sheet.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#55 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKjEpCUqZKAjVjxyZkeJlJkTpgTOcm8zks5q20YagaJpZM4Js4td
.

@bobismijnnaam
Copy link
Collaborator

This was all just to find an example of an rdf model that works. So yeah, a diagnosis I guess. And indeed after I did all that the NCF parsed the rdf completely. The RDF was still generated by the old editor though, not the new one.

The weird thing is the doctype declaration between the xml header and the rdf tag.

@bobismijnnaam
Copy link
Collaborator

The original editor exports a vt_has_fraction="1" property when you add value transactions. However our ontology does not have any vt_has_fraction property (that is, E3value.vt_has_fraction does not seem to exist). Should we add it by hand?

@bobismijnnaam
Copy link
Collaborator

Well, turns out Jaap's code barfs when the vt_has_fraction property is not present. So I'm just gonna add it now (ProfGenerator.java:2110)

@bobismijnnaam
Copy link
Collaborator

NCF module purrs without errors. No clue if the output is correct though (see slack for debug output & xls). As of: bdee357.

@danionita
Copy link
Owner Author

Somehow I missed these last updates. All looks good.
The transaction editor (issue #90 should allow the user to change the vt_has_fraction property

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

No branches or pull requests

2 participants