TINP changes: Difference between revisions

From tango.info wiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
see also [[TIN fix]], [[TIN]].
see also [[TINP fix]], [[TINP]].


Some of the TIN fixes are needed to avoid misstagging, e.g. a user has a correct [[GTIN]], and tango.info has wrong meta data, maybe a whole different got that GTIN. So the album formerly having that GTIN will then be related to a new [[TIN]].
Some of the TINP fixes are needed to avoid misstagging, e.g. a user has a correct [[GTIN]], and tango.info has wrong meta data, maybe a whole different got that GTIN. So the album formerly having that GTIN will then be related to a new [[TIN]].


Some changes change what performance a TINT refers to. Other only change performance data.
Some changes change what performance a TINT refers to. Other only change performance data.

Revision as of 2012-03-09T11:00:19

see also TINP fix, TINP.

Some of the TINP fixes are needed to avoid misstagging, e.g. a user has a correct GTIN, and tango.info has wrong meta data, maybe a whole different got that GTIN. So the album formerly having that GTIN will then be related to a new TIN.

Some changes change what performance a TINT refers to. Other only change performance data.

The latter are more frequent, and maybe the // unwanted to many, but I hope this will be fixed with new software and new performance name policy.

More problematic are the former ones.

Types and reasons

  • Fix1
    • Change reason: Wrong GTIN
    • Change type: GTIN -> part of existing GTIN
  • Fix3
    • Change reason: Invalid GTIN
    • Change type: Invalid GTIN -> valid GTIN
  • Fix5
    • Change reason: GTIN found
    • Change type: TINO -> existing(?) GTIN
  • Fix6
    • Change reason: Use TINO range, items are found to be part of collection
    • Change type: 2x (TINO -> TINO)