Pet Peeve: Vendor Documentation Naming Conventions

[Sal Ammoniac]

Why do vendors name documents something like 61105F.pdf rather than Timers.pdf, which reflects the content of the documentation? Why do they use these cryptic file names that only mean something to them? 

Download a bunch of documentation from one of these vendors and you'll end up opening a bunch of them until you find the one you need via trial and error. I usually end up renaming the documents to something sensible, but that's something the vendor should have done from the start.

[Muxr]

It's their numbering system, and sometimes they refer to those numbers in other documents so it can be useful in tracking down information. Usually what I do is when I save PDFs I append the description of it to the name.

[zapta]

Why do vendors name documents something like 61105F.pdf rather than Timers.pdf, which reflects the content of the documentation?

It's an easy way to generate compact and unique document ids.

[Sal Ammoniac]

Yeah, sure, but why not name the file "Timers-61105F.pdf" rather than just 61105F.pdf?

[obiwanjacobi]

Because they approached the problem from a technical perspective and not from a user perspective.
Its easier for the tech (dev) and harder for the user. If you want to make it easier for the user you have to put in more work and that costs more money. I believe this is true for all things.

[dadler]

The filenames are almost certainly automatically generated by their document management system.

However, I would be surprised if they could not configure the software to include some useful text in the filenames--however this data would have to come from somewhere. A human would have to assign it, or some script would have to try to extract a title from the document text.

There is good news though! You are allowed to rename the files after downloading them.

After downloading app notes etc, I highlight/copy the first bolded title I see in the document body, and rename the file to match that text.

[matseng]

This is a typical case of where the author/published of a document could have spent a few minutes extra to manually name the document to something relevant instead of having 10000+ readers each spend time renaming the file.

Basically the same thing when someone posts about an online meeting/webcast and says that is at 10am CDT and then having all the viewers to manually figure out when that is in their local time.  If the author had spent one minute creating a link https://www.timeanddate.com/worldclock/fixedtime.html?msg=My+Webcast&year=&month=&day=&hour=10&min=00&sec=0&p1=104&ah=1 and then just posted that as well, possibly shortened, life would much easier for the readers.

[neslekkim]

Since they take the time to make a list of documents like the reference manual here, it would't take too much more time to name the files also:
http://www.microchip.com/wwwproducts/Devices.aspx?product=PIC24FJ128GB204

For some reason, one of the documents have an reasonable name, section 34..

[westfw]

Mired in the old 8.3 filename syntax, perhaps?
I'm pretty happy with the new Atmel documentation filenames:

Atmel-42414-SAM-D09_Datasheet.pdf
Atmel-42366-SAM-BA-Bootloader-for-SAM-D21_ApplicationNote_AT07175.pdf

Unique numbers, meaningful titles, and even classification!