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

error due to duplicate OSSequenceNumber (but they belong to different strata) #187

Open
luciazarauz opened this issue Sep 26, 2023 · 3 comments
Assignees

Comments

@luciazarauz
Copy link

I am finding problems with the variable OSSequenceNumber.

I thougth this variable needed to be unique in each strata, reflecting the order os selection. In our case this order is not so relevant, as the selection methods is "NPQSRSWOR". But anyway, the upload is giving problems due to duplicates in this variable, but they are not real duplicates as the belong to different strata

You can find an exampe in the table below

image

Thanks!

@HenrikK-N HenrikK-N self-assigned this Sep 29, 2023
@HenrikK-N
Copy link
Collaborator

It has been agreed that each Onshore Event under a Design record should be uniquely by having a different OSsequenceNumber. At this point it will not be changed, but it can be taken up for discussion. Right now it is suggested to increase the OSsequenceNumber by one for each new Onshore Event.

@luciazarauz
Copy link
Author

ok!

@HenrikK-N
Copy link
Collaborator

The Core Group will go through the sequenseNumber for the Onshore Event, but more tables will be included in this task, we will return at a later date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants