Type-local NIDs provides an alternate ID mechanism for nodes. Each content type has its own separate, sequential ID number.

If configured for a site using the Casetracker module, nodes of the Case content type could be referenced by their type-specific ID instead of NID. (When I try to find a case by memory, I often bump into invalid case numbers on account of stray projects or blog entries.)

Comments

juampynr’s picture

Then, should we allow the user to select if he wants to reference ids by nid or lnid if this module is installed? Plus, what about UUIDs? Shall we consider this scenario too? I do not know if there are other modules which produce different ids.

Another question that rises is if this would make more sense to be done in freelinking module rather than in freelinking_casetracker so other plugins can benefit from it.

Grayside’s picture

Status: Active » Closed (won't fix)

This was kind of an idle thought. I'm comfortable dropping it. I think freelinking core is complicated enough without supporting integrations with modules that very few people will ever use.