PDF Disk Erasure Report Device Field

[FreeMinded]

When using ShredOS to do in-place wiping of devices it would be great if to have a field Device in the Disk Erasure Report PDF to link it to this device. We currently use the Customer field for that but it's a miss-use of that field and bit cumbersome as a customer has first to be added to the list before it can be selected.

[PartialVolume]

Can you give me an example as I'm not exactly sure what you mean. Thanks.

[FreeMinded]

@PartialVolume a think of a field identifying the device. This could be whatever a company uses as asset tag or device ID to physically identify a device. In our case that would be something like DZG5R7ZU or SRVCST01

[FreeMinded]

BTW: It would be great if that device field (if set) would be in the PDF filename same as the model and serial of the drive

[PartialVolume]

So automatically obtained from the dmidecode data which includes asset tags system serial number, UUID etc.?

[FreeMinded]

No, just a text field to fill manually.

[PartialVolume]

Yes, I think that could be done.The way I think it might work is at the drive selection screen you press 't' (for tag) you then enter the text you want. This tag field will then appear somewhere on the PDF. I'm not sure where that might be but may have to reduce the line spacing a small amount to fit a extra line in. Does that sound ok?

[PartialVolume]

Maybe in the header under drive model and serial number? Which would make it a lot easier as I wouldn't have to mess about with the line spacing in the body of the PDF.

[FreeMinded]

Yes, I think that could be done. The way I think it might work is at the drive selection screen you press 't' (for tag) you then enter the text you want. This tag field will then appear somewhere on the PDF. I'm not sure where that might be but may have to reduce the line spacing a small amount to fit a extra line in. Does that sound ok?

In our use case the Device would be global for all drives as it's used for in-place wiping of servers and clients. So in case of client devices they usually have one drive. But in servers there are often many and you should not be required to enter the device tag for every single drive.

[PartialVolume]

That's correct, the tag would be system specific and not drive specific. I.e the tag would apply to the whole system including all the drives. There wouldn't be separate tags per drive. I was also thinking that when it comes to entering the tag info, I might provide the option that you can manually enter your info or you can select from various fields of the dmidecode. This might be useful for those that want a asset tag or system serial number to occupy the tag field. Still of course providing the option to manually enter the data as on a lot of more obscure systems the manufacturer or assembler fail to populate a lot of the dmidecode fields.

[PartialVolume]

Something like the following in the header on each page? Tag text user customisable.