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

Add 'preview' parameter to import API #2205

Open
Tracked by #7684
hornc opened this issue Jul 1, 2019 · 1 comment
Open
Tracked by #7684

Add 'preview' parameter to import API #2205

hornc opened this issue Jul 1, 2019 · 1 comment
Labels
Lead: @hornc Issues overseen by Charles (Staff: Data Engineering Lead) [managed] Module: Import Issues related to the configuration or use of importbot and other bulk import systems. [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]

Comments

@hornc
Copy link
Collaborator

hornc commented Jul 1, 2019

Is your feature request related to a problem? Please describe.

per suggestion in #977 With the push to get a better import pipeline, and the complexities of the existing duplicate matching system, which exists, but is not clearly documented (and is generally complex with many factors combining to often produce unexpected results): We need a preview function to allow us to test the result of new import data without actually adding or modifying existing records.

This will help import users in production, and developers working on improvements to the import system.

Describe the solution you'd like

preview=true parameter which can be passed into the /api/import endpoints which will preform the exact matching and give a response to indicate whether a Editions / Work / Author was matched, or would have been created as a result of the request.

Needs to be clearly distinguishable that items were not actually created.

Proposal & Constraints

Additional context

@hornc hornc added Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] Module: Import Issues related to the configuration or use of importbot and other bulk import systems. [managed] labels Jul 1, 2019
@hornc hornc self-assigned this Jul 1, 2019
@hornc hornc added the Priority: 1 Do this week, receiving emails, time sensitive, . [managed] label Jul 1, 2019
@hornc hornc added this to In progress in Continuous Import Pipeline Jul 1, 2019
@hornc hornc moved this from In progress to To do in Continuous Import Pipeline Jul 1, 2019
@hornc hornc moved this from To do to Backlog in Continuous Import Pipeline Oct 2, 2019
@xayhewalo xayhewalo added this to Un-Triaged in Triage Oct 18, 2019
@xayhewalo xayhewalo moved this from Un-Triaged to High Priority in Triage Oct 18, 2019
@xayhewalo
Copy link
Collaborator

Labeling as backlogged per it's category in the Continuous Import Pipeline project. Let me know your thoughts @hornc

@xayhewalo xayhewalo moved this from High Priority to Triaged in Triage Oct 21, 2019
@hornc hornc added Priority: 2 Important, as time permits. [managed] and removed Priority: 1 Do this week, receiving emails, time sensitive, . [managed] labels Nov 7, 2019
@mekarpeles mekarpeles added the Lead: @hornc Issues overseen by Charles (Staff: Data Engineering Lead) [managed] label Dec 18, 2019
@hornc hornc unassigned hornc Aug 19, 2020
@scottbarnes scottbarnes mentioned this issue Mar 24, 2023
35 tasks
@mekarpeles mekarpeles added Priority: 3 Issues that we can consider at our leisure. [managed] and removed Priority: 2 Important, as time permits. [managed] labels Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Lead: @hornc Issues overseen by Charles (Staff: Data Engineering Lead) [managed] Module: Import Issues related to the configuration or use of importbot and other bulk import systems. [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]
Projects
Triage
  
Triaged
Development

No branches or pull requests

3 participants