... although we could add a 'job-copied' keyword for "job-state-reasons" to record whether a copy has been made.
> On Jun 4, 2020, at 2:16 PM, Michael Sweet <msweet at msweet.org> wrote:
>> Smith,
>>> On Jun 4, 2020, at 2:04 PM, Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy at hp.com> wrote:
>> ...
>>> Your question led me to wonder if there are “job accounting” attributes (Job Status attributes) that indicate that a Job is a copy of another Job to construct the audit trail?
>>>> Not at present, although I do remember having a discussion about adding a "parent-job-id" attribute at some point for this very reason. It doesn't look like it actually made it into JPS2, so that might be something to consider adding for EPX. (and then parent-job-id and parent-job-uuid for "fun")
>>>> [S.Kennedy] I’ll add “parent-job-id” and “parent-job-uuid” to EPX. Should the parent also have a Job Status attribute “copy-job-ids” and “copy-job-uuids”?
>> No, that will make implementation a lot more difficult. Just have the child jobs track their immediate parent and the Client can build a tree out of it as needed...
>> ________________________
> Michael Sweet
>>>
________________________
Michael Sweet