When using nFiles variable, behavior varies between create and update modes
Closed this issue · 2 comments
When supplying a value for nFiles in the modifyPubmedDb function, it behaves differently for the create and update modes. In create, it will start at the end of the file list, whereas update will start at the beginning of the file list.
I'm not sure if this is as intended, but I remembered that originally it behaved as it does in create mode, but then you purposefully pushed a commit to change this but I'm not sure if it was left on purpose or by accident.
It's on purpose. It mostly matters for testing, but the update files really need to be processed starting with the earliest. It doesn't matter as much for the baseline files, but since the oldest pmids lack a lot of elements, the newer files are more representative.
Gotcha, just wanted to make sure that was the desired outcome. I'll close this out.