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

reconsider statementId length constraints #731

Open
kathryn-ods opened this issue Oct 23, 2024 · 0 comments
Open

reconsider statementId length constraints #731

kathryn-ods opened this issue Oct 23, 2024 · 0 comments
Labels

Comments

@kathryn-ods
Copy link
Contributor

Just noting that the statementId requirement of being 32-64 characters has been a bit challenging for Rachel and I when working with PSC/GLEIF mappings to BODS 0.4

  • @kd-ods suggested having a prefix "XI-LEI-506700GE1G29325QX363" as a UUID for GLEIF statementIds but that is 27 characters and made them too long.
  • @odscrachel has had some issues meeting the minimum length for statementIds when working with PSC data

I think the constraints make sense in that we want to make sure statementIds are sufficiently unique/not unwieldly. However there's a risk of frustration when trying to construct statementIds that are made up of useful information e.g. prefix + registration number + date. It's not ideal to remove useful info/add filler in these cases.

@kathryn-ods kathryn-ods changed the title statementId length reconsider statementId length constraints Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant