Sticker aliases for same sheet with different SKUs

[Chris Dee]

It seems more common now that different SKU numbers are used for sticker sheets in US sets vs. RoW sets.

For example, these two appear equivalent:
134071A / 24744 / 6142623 at Bricklink: https://www.bricklink.com/v2/catalog/cat...75870stk01
140413A / 24743 / 6142622 at Brickowl: https://www.brickowl.com/catalog/lego-st...4743-24744

Should we create aliases for all 23 stickers 6142623a => 6142622a, etc., or is this overkill? How else might a user know that the stickers for 6142623 already exist in the library as 6142622?

We have done this for older stickers where the design appears on multiple sheets, e.g. 003437b.dat => 003340a.dat.

[Gerald Lasser]

It seems more common now that different SKU numbers are used for sticker sheets in US sets vs. RoW sets.

For example, these two appear equivalent:
134071A / 24744 / 6142623 at Bricklink: https://www.bricklink.com/v2/catalog/cat...75870stk01
140413A / 24743 / 6142622 at Brickowl: https://www.brickowl.com/catalog/lego-st...4743-24744

Should we create aliases for all 23 stickers 6142623a => 6142622a, etc., or is this overkill? How else might a user know that the stickers for 6142623 already exist in the library as 6142622?

We have done this for older stickers where the design appears on multiple sheets, e.g. 003437b.dat => 003340a.dat.

isn't it so that one of them is printed on a transparent sheet?

Like those:
Transparent: https://www.bricklink.com/v2/catalog/cat...=0#T=C&C=0
Solid Colour: https://www.bricklink.com/v2/catalog/cat...=0#T=C&C=0


But I can't make out a difference between those that Chris posted.

[Willy Tschager]

Should we create aliases for all 23 stickers 6142623a => 6142622a, etc., or is this overkill? How else might a user know that the stickers for 6142623 already exist in the library as 6142622?

Yes. To say it in Mandalorian style: This is the way.

As I fell in this number trap I think it is vital.

w.

[Magnus Forsberg]

Should we create aliases for all 23 stickers 6142623a => 6142622a, etc., or is this overkill? How else might a user know that the stickers for 6142623 already exist in the library as 6142622?

Here is another example.
International Version - (27091/6155286)  https://www.bricklink.com/v2/catalog/cat...2055stk01a
North American Version - (27092/6181834)  https://www.bricklink.com/v2/catalog/cat...2055stk01b

IMO it is time to change strategy.
If the setnumber, design and usage is the same, a second SKU number should be allowed as a keyword.

[Gerald Lasser]

Here is another example.
International Version - (27091/6155286)  https://www.bricklink.com/v2/catalog/cat...2055stk01a
North American Version - (27092/6181834)  https://www.bricklink.com/v2/catalog/cat...2055stk01b

IMO it is time to change strategy.
If the setnumber, design and usage is the same, a second SKU number should be allowed as a keyword.

That would have been my suggestion as well, use the second number as keyword.

How shall we do it with transparent versions? Like for some of the train stickers?

[Chris Dee]

That would have been my suggestion as well, use the second number as keyword.

How shall we do it with transparent versions? Like for some of the train stickers?

I think transparent vs. opaque sticker versions should be separate part files, maybe with the patterned section subparted.

I'm not a fan of the !KEYWORDS solution as it does not really help users searching the library by sticker sheet 'part' number. Do any of the authoring tools even provide a KEYWORDS search facility?

[Magnus Forsberg]

Do any of the authoring tools even provide a KEYWORDS search facility?

Yes.
I added the alternate number as a keyword in these 4 stickers.

   

[Willy Tschager]

It seems more common now that different SKU numbers are used for sticker sheets in US sets vs. RoW sets.

For example, these two appear equivalent:
134071A / 24744 / 6142623 at Bricklink: https://www.bricklink.com/v2/catalog/cat...75870stk01
140413A / 24743 / 6142622 at Brickowl: https://www.brickowl.com/catalog/lego-st...4743-24744

Should we create aliases for all 23 stickers 6142623a => 6142622a, etc., or is this overkill? How else might a user know that the stickers for 6142623 already exist in the library as 6142622?

We have done this for older stickers where the design appears on multiple sheets, e.g. 003437b.dat => 003340a.dat.

Today I came across this: https://www.ldraw.org/cgi-bin/ptdetail.c...24787b.dat

which comes in an international and north american version:

https://www.bricklink.com/v2/catalog/cat...1200stk01a
https://www.bricklink.com/v2/catalog/cat...1200stk01b

I still believe that is vital to have an ALIAS for these stickers.

w.

[Max Martin Richter]

Today I came across this: https://www.ldraw.org/cgi-bin/ptdetail.c...24787b.dat

which comes in an international and north american version:

https://www.bricklink.com/v2/catalog/cat...1200stk01a
https://www.bricklink.com/v2/catalog/cat...1200stk01b

I still believe that is vital to have an ALIAS for these stickers.

w.

In my eyes an alias would be fine. As we do it with identical parts produced in different moulding units (transparent/solid colour), we can adapt this to the stickers.