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
We need to be able to easily detect when a publication record that has previously been imported into RMD has subsequently been removed from the import source (Activity Insight or Pure) so that we can then decide whether to remove that publication record from RMD. In order to accomplish this, we don't want to (or simply cannot) request the publication metadata directly from the Activity Insight or Pure APIs for each record since RMD contains hundreds of thousands of publication records. Instead, each time that we import publications from Activity Insight and Pure, we should cache the current list of publications that are available from each import source in RMD's database so that we can compare those lists to RMD's publication records later. In the case of Activity Insight, we also want to record the status (published, in-press, etc.) of the publications in its list at the time of each import.
The lists of import source publications should be associated with a record of the import itself. The record of the import should capture when each import process began and when it completed so that we know what lists of import source publications to use for comparison.
EricDurante
changed the title
Record current list of publications (and their status) with each AI and Pure import
Record the current list of publications (and their status) with each AI and Pure import
Jan 27, 2025
We need to be able to easily detect when a publication record that has previously been imported into RMD has subsequently been removed from the import source (Activity Insight or Pure) so that we can then decide whether to remove that publication record from RMD. In order to accomplish this, we don't want to (or simply cannot) request the publication metadata directly from the Activity Insight or Pure APIs for each record since RMD contains hundreds of thousands of publication records. Instead, each time that we import publications from Activity Insight and Pure, we should cache the current list of publications that are available from each import source in RMD's database so that we can compare those lists to RMD's publication records later. In the case of Activity Insight, we also want to record the status (published, in-press, etc.) of the publications in its list at the time of each import.
The lists of import source publications should be associated with a record of the import itself. The record of the import should capture when each import process began and when it completed so that we know what lists of import source publications to use for comparison.
This is prerequisite for #944.
The text was updated successfully, but these errors were encountered: