Problem: There doesn't seem to be a need to have two package-type status endpoints

Please describe the problem you'd like to be solved.

As a developer using the API I currently have to integrate two different calls to check Transfer or SIP status depending on where I expect processing to be in the Archivematica pipeline.

I may loop around checking Transfer status until it is COMPLETE. At which point, I might then monitor Ingest status until it is COMPLETE so that I can tick-off that the package (the AIP) was created and properly stored.

Describe the solution you'd like to see implemented.

I would like to be able to make a single call to a generic package endpoint whether I am looking at a Transfer or a SIP and retrieve the same status information.

As a consumer of the endpoint I would like to see returned:

Whether I am looking at a Transfer or a SIP.
Status, e.g. COMPLETE vs FAILURE.
Possibly the last Job that was completed or unsuccessful see: https://github.com/archivematica/Issues/issues/625.
Both the transfer uuid and the sip uuid.

A user would only need to submit one UUID and Archivematica would need to find a SIP or an AIP with the matching UUID and return the appropriate information.

Describe alternatives you've considered.

We could leave the two endpoints as-is. I just feel that a mechanism like this would help in the day-to-day running of Archivematica, and make engaging with Archivematica that much easier in tools such as the automation-tools.

Additional context

Nothing of note.

For Artefactual use: Please make sure these steps are taken before moving this issue from Review to Verified in Waffle:

All PRs related to this issue are properly linked 👍
All PRs related to this issue have been merged 👍
Test plan for this issue has been implemented and passed 👍
Documentation regarding this issue has been written and it has been added to the release notes, if needed 👍

archivematica / Issues

Problem: There doesn't seem to be a need to have two package-type status endpoints #626