search

azgs / azlibrary_webclient

Client for the azlibrary_api
0 stars 1 forks source link

Provide gems upload in form #3

Closed NoisyFlowers closed 4 years ago

NoisyFlowers commented 4 years ago

This is related to the azlibrary_api issue https://github.com/azgs/azlibrary_api/issues/63

NoisyFlowers commented 4 years ago

This is implemented in 974ce992d295ae9bc729f83a236357ed5bbf8b81, in conjunction with the azgs/azlibrary_api#63 commit 523e18ae9bcacdfcbe06ea153553ccc7636ac8a8 and the azgs/azlibrary_database#38 commits: azlibConfigGDB: 036917d, 795729f, 506600d, 3c3fd28 azlibAdd: 3fa3f62, ed4658b, 5e246cf

This is deployed to dev. End-to-end testing can be verified by attempting to create three collections:

1) Using Waterman_ncgmp09.gdb.zip. This will verify that existing ncgmp09 functionality still works. 2) Using Blythe24k-gdb.zip. This will verify that a correct GeMS file will import correctly. 3) Using Waterman_gems2.zip. This will verify that an incorrect GeMS file (missing required columns) will cause an error.

Blythe24k-gdb.zip Waterman_gems2.zip Waterman_ncgmp09.gdb.zip

NoisyFlowers commented 4 years ago

This, along with the sister issues in api and database, are now running on prod.

Test listed above all passed. Test in https://github.com/azgs/azlibrary_api/issues/63 passed.