suggestion: permanent infocenter links to product anomaly descriptions

[pabigot]

Now that the infocenter is available, please consider making product anomaly descriptions available at a permanent URL, e.g. infocenter.nordicsemi.com/.../PAN.

The frameworks I develop for Nordic chips generally include workarounds for relevant anomalies, and it would be very nice if I could add a link to a description of the anomaly from my framework documentation or comments in implementation related to the workaround, instead of having to copy the description or make the user download the PDF to determine whether it's relevant to their application.

[Øyvind Karlsen]

Hi,

Actually there are permanent links in the infocenter, however the url will not update. The workaround is this:

1. Navigate to the page that you would like to link to

2. Right click it in the Contens menu

3. Select copy link address, this will link directly to the page

Like this:

And here's the link.

Best regards,

Øyvind

[pabigot]

A more relevant link would be infocenter.nordicsemi.com/.../anomaly_832_20.html for nRF52832 PAN 20.

So it looks like this feature is ready for the nRF52 line, but the nRF51 PANs are still only available as PDFs within the info center, which was the point of my suggestion. If the v3.1 PAN could be released in infocenter format that would meet my needs.

[Øyvind Karlsen]

Those PDFs are directly linkable and hosted on infocenter though, they will not be downloaded to your system. Like this: LINK.

[pabigot]

I guess it's the difference between "minimum viable product" and "done well". Yes, you could make assumptions that a developer is willing to put up with gratuitously long URLs like infocenter.nordicsemi.com/.../nRF51822-pan_v3.0.pdf in comments, that the reviewer/maintainer has a browser has a built-in PDF viewer, and that she's willing to page through the thing to try to locate a specific anomaly. (Unless you also have a workaround to link directly to, say, PAN 73 in that PDF? Because the index isn't present when it's viewed in Chrome nor are there internal links that work, and the PANs aren't in numerical order in the document.)

My point was simply that it could be done much better.

[Øyvind Karlsen]

I think we're on the same line now, and I agree with what you are saying. I will forward this to the relevant people.