We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
id
I hadn't realised, but in the legacy data abbreviated versions of the name of the organisation/vault are present in the id field.
So, when creating these two resources users need to be able to specify the value to be used as id.
In the edit form they should be editable, but should carry the same "edit carefully" warning we show for the catCode etc tables.
edit
Update: I'm consciously deferring this for a future development cycle, since it is unlikely that new orgs or vaults will be added anytime soon.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I hadn't realised, but in the legacy data abbreviated versions of the name of the organisation/vault are present in the
id
field.So, when creating these two resources users need to be able to specify the value to be used as
id
.In the
edit
form they should be editable, but should carry the same "edit carefully" warning we show for the catCode etc tables.Update: I'm consciously deferring this for a future development cycle, since it is unlikely that new orgs or vaults will be added anytime soon.
The text was updated successfully, but these errors were encountered: