Image Attachments section redesign

[artiomello]

NetBox version

v4.1.6

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

I believe the Image Attachment section needs to be revised to have it reflect data a bit more concisely, and precisely at that.

1. Image size

Size needs to be shown in MB, not in bytes. I'm almost 40 now and even I can't recall a single time in my life where image size in bytes would make any sense to me. Let alone now.

---

2. Name and Image columns

I think only one of them actually needs to stay. If you give a name to an image during upload - it's renamed accordingly, and the new name displayed in both columns. If you don't give a name, then the file name is taken and is displayed only in the Image column.

You can't have a situation where these two properties would be different, rather (and weirdly enough) omitted in some cases. So, they're pretty much the same. Hence having both of them doesn't make much sense.

---

3. Referencing image attachments in other objects and views

So, if we open any object that has image attachments like this one, that has two:

We see that it likely filters that same original image table with itself, and we get the same columns as in the original table:

Only here this information is completely redundant:

• We already know its name and that it's a site. Showing these properties here would make sense only in case it would show images for the site's child objects (which it should definitely not).
• The image/name pair is redundant, as described above.
• The size in bytes looks more like a phone number than anything else.
• All in all, this redundant information just adds more clutter to the object's page.

What really should be displayed here are:

• Name (serving as a pop-up image window).
• Size (in MB, obviously).
• Creation timestamp.

Use case

Updating this table, its object properties and how they are presented in other views/objects would make certain netbox pages less cluttery and more concise, showing only that which has value. This is especially true when viewing some more data rich objects, such as sites and racks.

Less is more, as they say.

Database changes

No response

External dependencies

No response