punkish / zenodeo

`nodejs` interface to Zenodo/BLR community
https://zenodeo.org
Creative Commons Zero v1.0 Universal
6 stars 1 forks source link

Ability to track parts of a treatment #17

Open gsautter opened 5 years ago

gsautter commented 5 years ago

Ability to track parts of a treatment

(6) This was simply old(er) markup from when we didn't ad the authorities yet (April 2016). I now ran the respective gizmo on the parent article, so the authority information is there. If you detect similar treatments, please let me know, so I can run that gizmo on them as well ... merely a single-line command to the server side batch.

This is precisely the reason I need to be able to track parts of a treatment. If someone detects and reports an error in a treatment, and then you rerun your extraction process on that treatment to correct the error, I need to be able to change only that treatment and its related parts. I can only do that if I can uniquely identify them. Timestamp is not the way to do that. The only sure way and one that makes a programmer's life easy is by being able to identify them uniquely with a primary key (in this case, the PK is the combo of the treatment ID and the ID of that specific part of the treatment).

Also, please note that under ideal circumstances, I really won't detect any such errors because the extraction process will run automatically without any intervention from me. In this case, I found it purely by chance because I wanted to examine my extraction logic on a single XML and I randomly happened to pick one that had this error. Under ideal circumstances, my extraction process will just silently move on.

Originally posted by @punkish in https://github.com/punkish/zenodeo/issues/14#issuecomment-515290624

gsautter commented 5 years ago

This is why subSubSections also have an id attribute now. Again, see http://treatment.plazi.org/GgServer/zenodeo/038787DAFFF7FF904BBFF925FD13F9AA , as well as #16