TINP deprecation: Difference between revisions

From tango.info wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:


For each 1:1 replacement (full product gets a new TINP and the new TINP only refers to that product) deliver the new TINP for any TINT-specific tag-set.
For each 1:1 replacement (full product gets a new TINP and the new TINP only refers to that product) deliver the new TINP for any TINT-specific tag-set.
To be decided:
* name of the variable to obtain the new TINP
Proposals:
* tinp_replacement
* tinp_new
==Database design==
Create a new table named "tinp_replacement" or similar.

Revision as of 2013-03-02T20:24:47

P R O P O S A L

This is related to TINP fix.

Proposal:

  • store the new TINP values in the DB
  • deliver them via the tagger

For each 1:1 replacement (full product gets a new TINP and the new TINP only refers to that product) deliver the new TINP for any TINT-specific tag-set.

To be decided:

  • name of the variable to obtain the new TINP

Proposals:

  • tinp_replacement
  • tinp_new

Database design

Create a new table named "tinp_replacement" or similar.