DeviceAllocationMapper missing?

[woodiecm]

Hello,

Is there a reason why a DeviceAllocationMapper hasn't been implemented yet? When I currently export an ISOXML, WAN elements arrive in the TSK, but no DAN. The WorkerAllocationMapper already exists.

[kelly-nelson]

Most of the work on this plugin has focused on transforming from ISOXML to ADAPT. While some work has been done in the other direction, that has not been a focus for any contributors, at least in recent years.

In the case of completed tasks, I personally have not found the DAN element to be consistently or reliably used, and it is somewhat redundant to examining the DET references on the DLVs that actually show up in the TLG data. As I recall, this is how the plugin works on the ISO->ADAPT direction.

For planned tasks (the more common ADAPT->ISO case), it is common that specific machinery details are unknown at the time of prescribing the task. While ISOXML does allow for this, it just hasn't come up yet as a use case that anyone has had.

You are welcome to PR an implementation for the DeviceAllocationMapper that fits your use case(s). Please PR into the Development branch.

[woodiecm]

I want to use it as a converter between John Deere and ISOXML. Since my software already fully processes ISO XML, I would save a lot of time by not having to integrate the ADAPT model now.
John Deere is the last major manufacturer that doesn't natively use ISOXML, and implementing the ADAPT model just for John Deere's sake would be too costly.
I'll take a look at how much implementing DAN in the plugin would cost and whether it would include all the important data.