Snapshots needs Statuses

[TiSiE]

We've implemented the ability to create snapshots of entities via:

• Core/SnapshotInterface
• Core/SnapshotTrait

and currenttly used in the Jobs module:

• Jobs/JobSnapshot

Snapshots (specifically the SnapshotMeta embedded document) is draftable to distinguish between active (unmerged) and merged snapshots.

As it is showing now, in the context of the jobs module, this is not enough. We need specific statuses of the snapshots to determine wether they were accepted, rejected, active.

So Snapshots needs to be State-Aware, which can be easily added with Core/StatusAwareInterface, Core/StatusAwareEntityTrait and the companion, Core/StatusInterface, respective Core/AbstractStatusEntity

What needs to be done:

1. Make snapshots (at least the JobSnapshot entity) status-aware.
   This can be done by adding the status directly to the snapshot entity (overriding the status from the original entity - which must not be altered by the snapshot anyway) or in the SnapshotMeta document.
   (This needs to be discussed further)
2. Make JobSnapshot Status entity with approppriate states
   • ACTIVE (UNMERGED)
   • ACCEPTED (MERGED)
   • REJECTED
3. Set the respective status upon actions taken on the snapshot either by the recruiter or by the admin
4. Show the current status in the recruiter's job list (and in the admin's job list)

---

Related classes to look at:

• Jobs/ManageController
• Jobs/InitialzeJob plugin
• Core/SnapshotRepository
• Jobs/view/index/index.ajax
• Jobs/view/admin/index.ajax

[TiSiE]

@kilip @fedys Whoever yells first may do this 😉

[cbleek]

Hi @kilip

do you have time to do this task?

I'll need @fedis to do some final task concerning the SimpleImport module.

[cbleek]

Hi @kilip

is the task description from TiSiE ok?

regards, carsten

[kilip]

Hi @cbleek , @TiSiE
I start working on this issue now.

[TiSiE]

@kilip Did you do anything yet? It would be nice to send a pull request, if so.... If not, you do not need to do anymore.