seed
seed copied to clipboard
SEED-platform
Can't set up the DQ rules for an imported file until you have imported it because the program won't know the field names
Expected Behavior
I want to set up DQ rules in the DQ Admin screen for a file I am going to import. But I haven't imported it yet, so the program doesn't know what fields are in it (at least the fields that are put in extra_data, which can be almost all of the fields in some cases), so I can't select the fields to set up the DQ rules.
Not sure we can deal with this situation but it's an interesting conundrum ! I encountered it while trying to test the DQ Admin world on a new file that hadn't been imported before with fields that were not standard fields.
Actual Behavior
N/A
Steps to Reproduce
N/A
Instance Information
Instance: dev1 SHA: ?? get an error; whatever the SHA is on 8/7/2018 at 6:40 pm PDT
Yeah this was a known challenge from the beginning. I think we just need to update how we recommend people upload their data.
I think the workflow would be to upload a few rows of data to “initialize” the columns and column mappings. They should also set up the list settings since that can significantly reduce the inventory list load times and is much easier to do when there is less data. At that point they can then upload the larger data file. On Tue, Aug 7, 2018 at 19:41 RDmitchell [email protected] wrote:
Expected Behavior
I want to set up DQ rules in the DQ Admin screen for a file I am going to import. But I haven't imported it yet, so the program doesn't know what fields are in it (at least the fields that are put in extra_data, which can be almost all of the fields in some cases), so I can't select the fields to set up the DQ rules.
Not sure we can deal with this situation but it's an interesting conundrum ! I encountered it while trying to test the DQ Admin world on a new file that hadn't been imported before with fields that were not standard fields. Actual Behavior
N/A Steps to Reproduce
N/A Instance Information
Instance: dev1 SHA: ?? get an error; whatever the SHA is on 8/7/2018 at 6:40 pm PDT
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/SEED-platform/seed/issues/1693, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0amvAH8pPlD6dDoR6VTx8BrYFNITsuks5uOkGugaJpZM4VzIz_ .
Yes I think that makes sense. So it's a documentation / workflow process issue rather than a program issue.
I will assign this to myself and add a "Documentation" label to it.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@nllong -- I guess I will document the solution you mention, although it is not a great solution from a user's standpoint.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
@isalanglois -- it is still a problem. Similar to what I was talking about yesterday that you can't rename your matching fields until you have imported your first set of data, where you have to give it one of the canonical matching field names.
Not sure how to resolve it but we need to rethink how users set up their fields -- right now the program does it from imported data. We may need to have a step that precedes that with some steps where the users can define the fields before they are imported in a file. This needs some design.
I'm going to investigate this to see if I can come up with a better solution since I'm working on the task of making it easier to setup a new organization with a lot of existing data.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.