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.

Sign up for GitHub

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

Jump to bottom

Legacy data #115

Open
AZlaserchron opened this issue Sep 30, 2016 · 1 comment
Open

Legacy data #115

AZlaserchron opened this issue Sep 30, 2016 · 1 comment
Assignees
@bowring
Labels
enhancement

Comments

@AZlaserchron
Copy link
Collaborator

When creating a new legacy data entry and trying to upload to sesar/geochron there is a problem with getting an IGSN.

I think that if we have the same option here as we do when we are putting data up to geochron after we reduce it. This would make this process much smoother.

So, if we can get a field to validate our geopass and then have sesar make an IGSN for our legacy data
@bowring bowring self-assigned this Oct 1, 2016
@bowring bowring added the bug label Oct 1, 2016
@bowring
Copy link
Member

bowring commented Oct 1, 2016 •
edited
Loading

This is addressed in 3.6.7 - due 3 Oct. and will be fully solved in a future release.

@bowring bowring added enhancement and removed bug labels Oct 2, 2016
@bowring bowring mentioned this issue Oct 3, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bowring bowring

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bowring @AZlaserchron