Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

CSV files already used in other projects are not linked again #26

gregjan opened this Issue Jun 7, 2011 · 2 comments


None yet
1 participant

gregjan commented Jun 7, 2011

Still seeing WB pull CSV files from previous projects (when trying to use the same CSV files for multiple projects). Current fix: wipe all old projects from WB before using CSV file again.

@ghost ghost assigned gregjan Jun 7, 2011


gregjan commented Jun 7, 2011

I may have already addressed this issue in the new code, at least I don't see evidence of it in testing. There is a confusing drop-down for "project" on the crosswalk creation wizard's first page. It has not been doing a good job of detecting the project automatically, and therefore has been usually preset to the first project in the list. This may have been a problem for usability.
I made it auto-detect the project more reliably from the current navigator selection.. I've walked through "many projects, same CSV file" scenarios a few times now and cannot replicate. I'll keep trying. It might easily be already fixed in the new code or else I need more help to replicate the issue.


gregjan commented Jun 10, 2011

I am seeing the expected behavior in the following 2 project 1 CSV tests:

  • on a Mac
  • capturing directly from G
  • staging in CDR DEV

Both projects have their own "link" to the same CSV file. Both crosswalks have that project's CSV file listed as the data source. Both crosswalks are producing and matching the appropriate MODS records. I am closing the bug for now. Please reopen if BETA testing reveals it again.

@gregjan gregjan closed this Jun 10, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment