v0.4.0

This returns everything the v1 api does, but it adds one more endpoint:

/api/v2/users/orcid/{orcid}/groupdetails

This returns a list of beamlines and proposals in separate lists, and a list of ESAFs in a small "summary" format that indicates the roles of the user in that esaf: 'pi', 'explead', or 'participant'.

This is enough information for a back-end service to:

1. Create internal records for Beamlines if missing
2. Create internal records for Proposals if missing
3. Create internal records for ESAFs if missing (and connect them with Proposals)

And then link the given user with these records.
The v1 API wasn't quite adequate for my purposes because it mixed Beamlines, Proposals, and ESAFs together, and stripped out all the context for them. This v2 API endpoint is being used by the Dataset Tracker back end after it authenticates via ORCID.

v0.3.5

Full Changelog: v0.3.4...v0.3.5

v0.3.4

Full Changelog: v0.3.3...v0.3.4

v0.3.3

What's Changed

• Alternate dockerfile by @GBirkel in #8

Full Changelog: v0.3.2...v0.3.3

v0.3.2

Full Changelog: v0.3.1...v0.3.2

v0.3.1

Full Changelog: v0.3.0...v0.3.1

Fixes docker image

v0.3.0

What's Changed

• fix esaf/proposals none issue by @dylanmcreynolds in #1
• fix login check by @dylanmcreynolds in #2
• protect against not being in admin group by @dylanmcreynolds in #3
• protect against beamline roles being empty by @dylanmcreynolds in #4
• added test script and logging by @dylanmcreynolds in #5
• Support functions get_user_proposals and get_user_esafs now use ORCID instead of LBNLID. by @GBirkel in #7

New Contributors

• @dylanmcreynolds made their first contribution in #1
• @GBirkel made their first contribution in #7

Full Changelog: v.0.2.0...v0.3.0