TINP changes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
More problematic are the former ones. | More problematic are the former ones. | ||
== Types and reasons == | |||
* Fix1 | * Fix1 | ||
** Change reason: Wrong GTIN | ** Change reason: Wrong GTIN | ||
| Line 16: | Line 17: | ||
** Change type: Invalid GTIN -> valid GTIN | ** Change type: Invalid GTIN -> valid GTIN | ||
* Fix5 | * Fix5 | ||
* Change reason: GTIN found | ** Change reason: GTIN found | ||
* Change type: TINO -> existing(?) GTIN | ** Change type: TINO -> existing(?) GTIN | ||
* Fix6 | * Fix6 | ||
* Change reason: better TINO range | ** Change reason: better TINO range | ||
* Change type: 2x (TINO -> TINO) | ** Change type: 2x (TINO -> TINO) | ||
Revision as of 2011-03-25T13:36:41
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 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: better TINO range
- Change type: 2x (TINO -> TINO)