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

Not all fields included in batch upload templates are accessible via ATTAINS web services #554

Open
hillarymarler opened this issue Dec 13, 2024 · 0 comments
Labels
Future Improvement Minimum viable function complete, issue includes potential future improvements Module 3 More Research Needed TADA Team Discussion Usability

Comments

@hillarymarler
Copy link
Collaborator

Not all fields included in batch upload templates for ATTAINS are accessible via the web services (ex: Assessment Unit Comment, Assessment Comment). All of the fields non-accessible via web services that I have observed so far are "optional" fields.

This means that we could recreate batch upload templates that would work, but if a user uploaded them to ATTAINS, any data that had been included in those optional fields would be overwritten (NULL).

A couple of options to work around this:

  • Require users to download the required data sets from ATTAINS and import them as part of their work flow (then ATTAINS web services would not be accessed, all necessary information would be obtained from these user-supplied files)
  • Set up work flow to rely primarily on ATTAINS web services. Print a warning message to users that they will need to use an additional function to append comments and other non-public fields to their batch upload files. To run this helper function, they would need to download the appropriate data set from ATTAINS and use it as a param in the function.
@hillarymarler hillarymarler added Future Improvement Minimum viable function complete, issue includes potential future improvements Usability TADA Team Discussion More Research Needed Module 3 labels Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Future Improvement Minimum viable function complete, issue includes potential future improvements Module 3 More Research Needed TADA Team Discussion Usability
Projects
None yet
Development

No branches or pull requests

1 participant