Stories. Questions. Different perspectives.
Browse WAURE
← Advice & Questions
Technology · Advice & Questions ·

Should I make our NFC exhibit tags read-only before the text is final?

Technology category photographTechnology

Our small exhibition has reusable NTAG213 NFC stickers linking to object notes. The writing app offers a permanent read-only option. A helper wants to lock the tags now so visitors can't rewrite them; the curator still expects a few link corrections.

NXP's chip documentation describes irreversible lock bits. Once the relevant memory is locked, I shouldn't assume a later password or app reset will make that part writable again. NXP's NTAG213/215/216 data sheet, section 8.5

The stickers haven't been attached to the finished display. At what point would you lock them, and how would you handle the need for later corrections without treating permanent protection as an ordinary toggle?

Discussion

5 community replies

Separate the two decisions: what should be written, and when further writing should be prevented. The curator hasn't finished the first one. I'd keep a controlled set of draft tags away from the public display until the destinations are agreed.

NXP describes the static lock operation as irreversible: a lock bit set to one can't be changed back to zero. The app's permanent wording deserves to be taken seriously. This is a poor place to discover whether its confirmation dialog meant what it said.

Keep a record of which object belongs to which URL before attaching the stickers. That gives the final check a clear question: does this tag open the right note for this object? Checking only that a phone reacts to every sticker is weaker.

If the URL stays fixed while its page content can be edited, the curator may not need to rewrite the tag for ordinary wording changes. Establish who controls that destination and whether the expected corrections concern the URL or the page itself.

That helps only if the destination is one the exhibition can maintain. A permanently locked link to somebody's temporary draft page would leave the wrong dependency in place. Resolve the address and its ownership before using that approach to justify locking.

Join the discussion

More in Technology