Redisplay Messages: Compact | Brief | All | Full Show Messages: All | Without Replies| Author: | Admin_Russell  | | Posted: | Mar 22, 2024 22:00 | | Subject: | Re: Seller Verification | | Viewed: | 175 times | | Topic: | General | |
| In General, par016 writes:
| | I didn't have to do any verification like that. Honestly without knowing
exactly what you are describing, it sounds a bit like further phishing. My verification
was only in an email from Russell. As for response time, unfortunately, I was
hacked at 1030PM and had to fend off the hacker for 7 hours while I waited for
an admin to wake up lol
|
FYI I think we've got Rick's situation sorted out.
Our admin staff does not have access to the communcations with various members
over the years, so they cannot act as quickly or with as much confidence. Because
of the sensitivity of the situation, they follow a strict protocol that puts
security above everything else.
|
 |
| Author: | Admin_Russell | | Posted: | Mar 21, 2024 15:58 | | Subject: | Re: WARNING! Login from new device phishing emai | | Viewed: | 97 times | | Topic: | Problem | |
| In Problem, Saitobricks.ca writes:
| | In Problem, Admin_Russell writes:
| | In Problem, randyf writes:
| | In Problem, chetzler writes:
| | I don’t know why BrickLink has suddenly become such a juicy target.
|
All of it started fairly shortly after all of the extremely unpopular part merges
started to actually occur. I have a strong feeling that a user here that was
very upset about the decisions made is having some "fun" at BrickLink's
expense.
|
Interesting theory. But the scammers that caused the November 3 incident are
the same ones that caused the problems last night, and the variant merge project
was not exposed to the public before January 2024.
As much as companies tend not to boast about the number of online attacks they
receive, we do see a remarkable increase in scammer activity across the board
- throughout many companies and across different industries. To us, it does not
feel like BrickLink is being singled out.
|
Does there happen to be a plan in the works to stop this activity?
|
Yes. In fact, most of what is being done to prevent this type of fraud is being
done behind the scenes, and BrickLink members are not aware that it is happening.
|
|
| Author: | Admin_Russell | | Posted: | Mar 21, 2024 15:44 | | Subject: | Re: WARNING! Login from new device phishing emai | | Viewed: | 96 times | | Topic: | Problem | |
| In Problem, randyf writes:
| | In Problem, chetzler writes:
| | I don’t know why BrickLink has suddenly become such a juicy target.
|
All of it started fairly shortly after all of the extremely unpopular part merges
started to actually occur. I have a strong feeling that a user here that was
very upset about the decisions made is having some "fun" at BrickLink's
expense.
|
Interesting theory. But the scammers that caused the November 3 incident are
the same ones that caused the problems last night, and the variant merge project
was not exposed to the public before January 2024.
As much as companies tend not to boast about the number of online attacks they
receive, we do see a remarkable increase in scammer activity across the board
- throughout many companies and across different industries. To us, it does not
feel like BrickLink is being singled out.
|
|
| Author: | Admin_Russell | | Posted: | Mar 21, 2024 04:53 | | Subject: | Re: HELP HACKED (Some new info) | | Viewed: | 110 times | | Topic: | General | |
| In General, par016 writes:
| | In General, Nubs_Select writes:
| | In General, Nubs_Select writes:
| | In General, Chickaroo writes:
| | In General, Nubs_Select writes:
| | In General, Chickaroo writes:
| | In General, kittybrickz writes:
| | I'm heading to bed, best wishes to a speedy resolution.
Goodnight and sweet dreams of paid orders, positive feedbacks and pizza, to everyone
who isn't a HACKER 
|
Night!
I’ve got the coffee on for anyone who is still up
Roo 
|
Do you have tea? I’m still up for about an hour and a little
|
I think you need the one on the right Nubs!
Roo
|
|
Well I’m off for a short bit. Hopefully your are able to get it resolved soon!
|
Thanks for the company! He's been quiet for a while now. Probably hoping
to lul me into complacency, but I'm still refreshing constantly. The next
admin shift can't come soon enough
|
I have taken control of your account and sent you a message using an old email.
If you don't get my message, contact me at admin@bricklink.com
|
|
| Author: | Admin_Russell | | Posted: | Mar 19, 2024 11:09 | | Subject: | Re: Need "Item For Sale Condition" Clarification | | Viewed: | 113 times | | Topic: | Selling | |
| In Selling, aaronaar writes:
| | In Selling, aaronaar writes:
| | Hi!
I didn't get a response from the help desk, so I'm asking here.
I noticed that I can part together some official sets using 100% new parts. Am
I allowed to list those sets as "new incomplete" if I mention in the
comments that I parted together the set myself using new parts and am missing
box/instructions/stickers? Or are you only allowed to list a set as "new
incomplete" if you only took items out of a NISB set?
If you are not allowed to list it as "new incomplete", could you list
it as "used incomplete" and say in the comments that you parted it together
using new parts and am missing box/instructions/stickers?
Given that:
"Custom sets or instructions may be listed, provided they do not infringe
on any intellectual property rights, including those of the LEGO Group."
I do not believe I could list it as a custom set instead?
Thanks for information and if possible would like clarification from an admin.
|
Upon further investigation I have found at least one lot
https://store.bricklink.com/SortStation?itemID=336122737#/shop?o={%22invID%22:%22336122737%22}
where this exact scenario is listed as “new incomplete” and it has been listed
for over a year.
Wether this is due to it being allowed or simply never noticed is up for debate.
|
The big question here is whether that tile is original. There have been a few
fakes sold on BrickLink over the years before we caught them, so maybe it's
one of those.
In general, we do frown on used sets that have been BrickLinked, especially some
of the highly collectible ones like this:
But we don't proactively remove them. If they get reported, they will get
taken down though.
If someone wants to sell a collection of parts that may or may constitute a complete
set, they can always list it as a custom lot.
|
|
| Author: | Admin_Russell | | Posted: | Mar 18, 2024 10:44 | | Subject: | Re: Selling Removed Stickers | | Viewed: | 114 times | | Topic: | Selling | |
| In Selling, zorbanj writes:
| | In Selling, brickerking writes:
| |
So just to follow up on this one...
I asked the help desk:
Can I list an incomplete set of peeled off stickers stored on wax paper as a
used sticker sheet with notes and a photo?
They got back to me and said it would need to be listed as a custom item.
So then I reported a couple other stickers listed in the above condition and
they were all removed from the store within a couple days.
|
The help language was changed:
https://www.bricklink.com/help.asp?helpID=102
It now reads (second sentence is new):
"Sticker sheets missing stickers must be listed as used. Individual stickers
not attached to the original sticker sheet must be listed as Custom Items."
|
Yes, as a result of the complaints against these sticker listings, we have decided
to address the issue in the listing rules.
The main problem with individual stickers separated from the sheet is that we
don't have catalog entries for them. It is simply a practical concession
that we allow sheets with missing stickers to be sold as used, since for the
most part, used complete stickers sheets are very uncommon and of questionable
market value.
In the listings that were pulled down, the used stickers were placed on felt
and this is not great, with the fibers from the felt getting stuck to the back
of the sticker. Wax paper (freezer paper) is better since this is similar to
the surface the stickers were originally stuck to.
However, I do believe there is a valid market for used stickers for vintage sets,
especially some of the plastic based stickers (e.g. Fabuland). So I will be consulting
with our Marketplace and Catalog teams to see if we can make a provision for
listing them in some way under the sticker entry and not as custom items.
Until we make a decision on this, we won't be removing any more used sticker
listings.
|
|
| Author: | Admin_Russell | | Posted: | Mar 15, 2024 21:25 | | Subject: | Re: Address change that I didn't make? | | Viewed: | 86 times | | Topic: | Problem | |
| In Problem, jasonpenn writes:
| | First screenshot is my actual address 3120 Cuervo on the Feb 11th order and the
Second is a combination of my old address 12817 Roma and my new address 3120
Cuervo on the March 4th order. I didn't make the change in between. I think
an admin needs to look into this because there was no date on the log of changing
my address in between
Jason
|
Your store address is still listed as the old one, btw.
|
|
| Author: | Admin_Russell | | Posted: | Mar 15, 2024 14:37 | | Subject: | Re: One time pin random generation | | Viewed: | 76 times | | Topic: | General | |
| In General, Saitobricks.ca writes:
| | In General, brickerking writes:
| | In General, Ianpugh writes:
| | Is anyone else getting random one time pin notifications? I’ve had about 6 sent
at times when i have not tried to log in to my account so far……. Not sure if
this is happening to everyone or just me?
|
They just turned that on for everyone without warning: https://www.bricklink.com/message.asp?ID=1459423
|
Yep, went to check my store settings and it was on. 
|
You can turn it off if you wish.
|
|
| Author: | Admin_Russell | | Posted: | Mar 14, 2024 17:40 | | Subject: | Expanded feature for power users | | Viewed: | 171 times | | Topic: | Catalog | | Status: | Open | |
| Hi everyone,
One of the side effects of the variant merge project is that some of our more
advanced users began asking for Alternate Item IDs to be included in the catalog
download feature.
So we have added this field to the download - see attached images. Downloads
(as before) are available in either CSV or XML format.
By way of reminder, for the variant project we are adding all original item numbers
as alternates to make sure people are able to easily find parts where the number
has changed.
|
|
|
| Author: | Admin_Russell | | Posted: | Mar 13, 2024 13:22 | | Subject: | Re: Is this a legit email? | | Viewed: | 110 times | | Topic: | Help | |
| In Help, adam.r writes:
| | I have received an email asking me to sign up to be a BrickLink Research Member.
Whilst I have no problem with being BrickLink's guinea pig however given
the recent warnings about phishing emails targeting BrickLink users, I figured
that it would be best to check if this is a legitimate email before signing up.
The Sign up! link goes to an Office 365 form that asks questions including Name,
Email address and BrickLink username.
Could someone from BrickLink please advise if BrickLink has indeed been sending
out such emails, or is someone else up to no good?
|
This is a legitimate email from our BrickLink team. Please sign up if you are
interested.
|
|
|
| Author: | Admin_Russell | | Posted: | Mar 11, 2024 13:34 | | Subject: | Re: Add links not working | | Viewed: | 50 times | | Topic: | Help | |
| In Help, randyf writes:
| | In Help, Admin_Russell writes:
| | In Help, Turez writes:
| | In Help, Saitobricks.ca writes:
| | I’m trying to add a link for Jangbricks channel for reference, but I tried to
add a link before and it didn’t go through.
Is there something I need to fill out for the link I don’t know about?
|
There is an issue with the image upload. Try adding the link without an image.
|
The image upload was just fixed last week.
|
So, it only took five months for the fix. That is pretty fast for BrickLink speeds.
|
Actually, the links image issue was reported in June of 2021. Definitely one
of the longer fixes.
|
|
| Author: | Admin_Russell | | Posted: | Mar 11, 2024 13:19 | | Subject: | Re: Add links not working | | Viewed: | 52 times | | Topic: | Help | |
| In Help, Turez writes:
| | In Help, Saitobricks.ca writes:
| | I’m trying to add a link for Jangbricks channel for reference, but I tried to
add a link before and it didn’t go through.
Is there something I need to fill out for the link I don’t know about?
|
There is an issue with the image upload. Try adding the link without an image.
|
The image upload was just fixed last week.
|
|
| Author: | Admin_Russell | | Posted: | Mar 5, 2024 12:05 | | Subject: | Re: Phishing email UPDATE March 5 | | Viewed: | 272 times | | Topic: | Administrative | |
| Hello again everyone,
Our security team was able to get the original bricklinks.net site taken
down, but we got reports this morning of a new bricklinks.org site and
evidence that phishing emails have been sent to our users, directing people to
this new site. The new site is much more realistic (see image below).
Please log in ONLY to bricklink.com and be aware that an effort is being
made to steal your BrickLink credentials. We will keep you updated if this problem
persists.
The BrickLink Team
|
|
|
| Author: | Admin_Russell | | Posted: | Mar 4, 2024 11:01 | | Subject: | Re: Variant merge - clarification 553b/c | | Viewed: | 114 times | | Topic: | Catalog | |
| In Catalog, jennnifer writes:
| | Hello,
[p=553b]
I see that the old 553b Blocked Stud has been merged with the much newer 3626
Vented Stud.
Was I wrong in expecting that it was also to be merged with 553c Hollow Stud?
Wasn't the point to not have to differentiate between the different stud
types?
Thanks,
~Jen
|
The big merges have not been finished yet. I need help from a developer to make
sure we don't shut down the servers with the merge operation.
|
|
| Author: | Admin_Russell | | Posted: | Mar 2, 2024 22:22 | | Subject: | Re: Seriously? | | Viewed: | 175 times | | Topic: | Catalog | |
| In Catalog, here4bricks614 writes:
| | In Catalog, Admin_Russell writes:
| | In Catalog, here4bricks614 writes:
| | What was the point of merging 44302 and 54657? The other hinge bricks/plates?
All of the element numbers are gone and now it’s going to be harder to find the
specific variant.
|
They are all here. They have to be added manually after the merge has run its
course. Because of a bug in the PCC upload process, it can be really tedious
to add many of these at once, so I break up the process a bit to keep my sanity:
https://www.bricklink.com/catalogColors.asp?itemType=P&itemNo=44302&v=2
If you spot some that are missing, please file a request to add them. Same thing
with any alternate part numbers. I am adding all original numbers as alternate
numbers so there shouldn't be any trouble with people finding things.
And for the other comments in this thread with concerns that the project is being
executed in a careless or haphazard way, I am working line by line through a
spreadsheet that was prepared and proofread weeks ago. Nothing has been merged
by mistake, and nothing will be.
Sometimes I will do things out of order, or leave a section partially done. This
is because of time (and I am quite behind on the project already) and because
of some technical limitations of the merge feature. There are several "big"
parts where I will need help from a developer to complete the merge without jeopardizing
site performance.
|
Why were the grooved variants merged?
|
Because they were on the list from the beginning:
https://www.bricklink.com/help.asp?helpID=2629
The reason they got on the list is because they are not classified as cosmetic
variants or typical grooved parts. The groove became apparent when the teeth
on the hinges was being examined, and the grooves were distinguished for the
same reason as the teeth. But when we remove the reason for recognizing the teeth,
we also remove the reason for recognizing the groove.
|
|
| Author: | Admin_Russell | | Posted: | Mar 2, 2024 22:14 | | Subject: | Re: Seriously? | | Viewed: | 227 times | | Topic: | Catalog | |
| In Catalog, here4bricks614 writes:
| | What was the point of merging 44302 and 54657? The other hinge bricks/plates?
All of the element numbers are gone and now it’s going to be harder to find the
specific variant.
|
They are all here. They have to be added manually after the merge has run its
course. Because of a bug in the PCC upload process, it can be really tedious
to add many of these at once, so I break up the process a bit to keep my sanity:
https://www.bricklink.com/catalogColors.asp?itemType=P&itemNo=44302&v=2
If you spot some that are missing, please file a request to add them. Same thing
with any alternate part numbers. I am adding all original numbers as alternate
numbers so there shouldn't be any trouble with people finding things.
And for the other comments in this thread with concerns that the project is being
executed in a careless or haphazard way, I am working line by line through a
spreadsheet that was prepared and proofread weeks ago. Nothing has been merged
by mistake, and nothing will be.
Sometimes I will do things out of order, or leave a section partially done. This
is because of time (and I am quite behind on the project already) and because
of some technical limitations of the merge feature. There are several "big"
parts where I will need help from a developer to complete the merge without jeopardizing
site performance.
|
|
| Author: | Admin_Russell | | Posted: | Feb 27, 2024 14:29 | | Subject: | Re: Special assembly item | | Viewed: | 68 times | | Topic: | Catalog Requests | |
| In Catalog Requests, Saitobricks.ca writes:
| | In Catalog Requests, richspin writes:
| | Thanks Saitobricks.ca but they don't show up there either.
|
Sorry wrong category, try going to the special assembly category.
|
Lot ID: 392424894
Lot ID: 392424541
|
|
| Author: | Admin_Russell | | Posted: | Feb 16, 2024 22:10 | | Subject: | Re: Seeing completed NSS | | Viewed: | 95 times | | Topic: | General | |
| In General, TheBrickGuys writes:
| | Is there any way for a store to see if they have ever had an NSS completed against
themselves?
Jim
|
No there, is not (at least not an easy way) but you can ask customer service
any time and they can provide a response.
We are considering sending out a notice after 2 NSS alerts are completed, just
as a warning to sellers. We understand that many NSS alerts are completed accidentally
by well-meaning buyers, and that a completed NSS does not necessarily mean that
a buyer was disenfranchised.
|
|
| Author: | Admin_Russell | | Posted: | Feb 16, 2024 22:06 | | Subject: | Reaction to the R.R. Slugger video | | Viewed: | 430 times | | Topic: | Catalog | | Status: | Open | |
| Hello again everyone,
This is my official response to the video from R.R. Slugger concerning the merging
of part variants in the BrickLink catalog:
https://www.youtube.com/watch?v=aGRxNX8Cg_o&t=1s
Here is an initial response to the video, specifically regarding the set inventory
for the Core Magnetizer:
https://www.bricklink.com/message.asp?ID=1450164
Here is today's response:
*************************************
I’ll start with a couple points I actually agree with Slugger on:
1) BrickLink certainly is an invaluable tool, and one of the things that has
motivated me to invest in the catalog over the years, long before I became a
community admin or started working in the BrickLink office, was knowing that
whatever corrections or additions I would make would instantly circle the globe
and potentially benefit thousands of fans everywhere.
2) Regarding the suggestion to double down on accuracy – that is actually what
we’re doing, if you look at the big picture. I remember discussing with one of
the authors of the LEGO Collector books that came out a few years ago:
and one of the points we discussed was why certain things weren’t included in
a publication that was so comprehensive. The answer was that if a particular
data field didn’t have at least 80% of the data, then there were questions raised
as to how useful that field would be.
Of course this case does not cover all of the changes being made to the BrickLink
catalog, but it does pertain to some of them. The smooth slopes and frosted bricks,
even after 20 years of accepting data from the community, have a very weak connection
to our inventory system. Many of the parts are not represented even a single
time, and of those that are represented, there are serious questions as to the
accuracy of the inventory change requests.
The biggest obstacle in separating variants on BrickLink, especially the older
ones, is lack of real data. So the question comes up, should we have entries
on BrickLink that can’t or never will be represented sufficiently in the inventory
system?
Being orphaned or partially orphaned from the system is a bad thing, and our
stance on that is one of the things that has really changed since Dan built the
inventory system in the early 2000s. It used to be acceptable to have entries
floating around just for buying and selling, but over time we have realized the
power of our inventory system, to the extent that we now use artificial inventories
to represent certain parts (like BAM parts):
By removing some of these variants, the accuracy and inclusiveness of the inventory
system goes up, and that is the primary driving force behind these current changes.
Why not just fill out the data instead of consolidating entries? Because we simply
do not have the data, and if we did, we couldn’t handle it all anyway. There
is no way we can add thousands of new minifigure inventories to the system simply
to accommodate different types of studs.
Next I’d like to give an actual example or something that WILL be lost in
the transition.
Slugger is right – just because the example he gave may not have been the perfect
example, it doesn’t negate the point that something will be lost. So here goes:
Set 7171 from 1999 (Mos Espa Podrace):
is one of the celebrated early Star Wars sets and as such we may consider it
to be at the pinnacle of collector interest. In that set is a yellow dome with
a “blocked open stud” which is part no. 30151a:
[p=30151a,3]
The next version of that part by all accounts was introduced around 2010,
[p=30151b]
and by that time, the Mos Espa Podrace had long been retired. So we can say with
reasonable certainty that this set came originally with domes with blocked open
studs. If you see a copy of the set sitting on someone’s shelf and the domes
on Anakin’s podracer have hollow studs (no little Mercedes symbol), that is a
sure sign that the parts, and maybe even the whole set, is not original.
So if the BrickLink catalog stops distinguishing the “a” from the “b” version,
someone might build it wrong and wouldn’t even know it! However, as a quiz question
for savvy readers, why would this scenario never actually happen in the real
world? What do we know about these the 30151 variants that puts this problem
completely into the realm of the hypothetical?
Next example, set 4778-1 from 2005 (Desert Biplane):
This is not Star Wars buts it’s still a classic in my book. There is a different
kind of dome on the front of this plane (553), but it has the same issues as
the previously mentioned dome part.
[p=553b,5]
This set is from 2005, so it’s not likely that it ever came with the “c” variant.
The 2008 appearance is in the first UCS Death Star which had a really long production
run and has over 50 lines of variants in the BrickLink inventory:
But if this little set were produced up through 2010, there might be a real possibility
of seeing one with a “c” variant.
[p=553c,5]
So with the current merges, this is data that would be lost. People wouldn’t
know about the stud variants, and someone could get any of 3 different stud types
– blocked open, hollow, or even vented. All three exist in red.
[p=3262,5]
Next up is set 6745-1 from 2009 (Propeller Power).
This also has a red 533 on the nose of the plane, but here the inventory system
says it could have either the “b” or “c” variant. Check the change log to see
if you recognize any of the people who added these variants to the set:
https://www.bricklink.com/catalogInvChangeItem.asp?itemType=S&itemNo=6745-1&viewDate=Y&viewStatus=1
We’re pretty sure this came with both “b” and “c” types. It didn’t come with
a vented stud, and someone might mistakenly put one on this model if BrickLink
doesn’t educate them about it, right? That is the premise on why we need these
variants in the catalog, correct?
The thing is, how can we tolerate the difference of stud type in this model,
and not in other models where it is historically incorrect? In this plane model
from 2009, both are correct, so what does that say about the mixing of variants
in other models?
True collectors know that there actually is no replacement part that will ever
perfectly replace a part that is lost. The only truly correct part is the part
the set originally came with. It’s nice to get as close as possible to a correct
replacement part, but it’s a futile attempt.
So I will admit that something is lost in the catalog by harmonizing all the
hollow studs types. But the second message is that whatever is lost is quite
unimportant in relation to the effort it takes for the BrickLink community to
recognize these variants.
We weighed it up, and decided that stud types are not important enough. They
have some importance, and there are some workarounds available for the people
who really want to go down that path. But overall, what we seem to be losing
is less than what we believe we are gaining.
**************************************
One more detail about the video – in navigating around the BrickLink catalog,
I noticed Slugger used the new inventory tab on the catalog page instead of the
proper inventory page accessible by the link at the top of the page.
https://www.bricklink.com/catalogItemInv.asp?S=6989-1
There are multiple problems with this version of the inventory. First, there
is no link to the change log, which for specialists is a must. Reading the change
log lets you determine the accuracy of the data you are consuming.
Second, the match IDs do not line up with the inventory notes, so any mention,
for example, of “match ID 99” (which is critical to understanding variant inventories)
doesn’t make any sense.
Indispensable
Some of my colleagues were surprised to see such a strong reaction from our users
on this topic. But the fact is, variants are an indispensable feature of the
BrickLink catalog and they are one of the main reasons for the “sealed set” standard
we maintain for new inventories. Keeping this standard comes at a cost, and it’s
important for people to know that all of this work and energy is appreciated.
https://www.bricklink.com/help.asp?helpID=1103
BrickLink is not descending into a parts oblivion where nothing is distinguished.
I made that very clear from the very first announcement. This is simply a mid-way
correction to enable us to do better at what we already do. I trust that over
the coming months and years you will come around to believing me on that point.
|
|
| Author: | Admin_Russell | | Posted: | Feb 16, 2024 14:57 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 75 times | | Topic: | Technical Issues | |
| In Technical Issues, DonnaxNL writes:
| | In Technical Issues, DonnaxNL writes:
| | Hi there,
I got notified by a Rebrickable customer who purchased moc instructions from
me that uploading of the XML file didn't work. After taking a look at it,
I noticed they were all parts that have a 'b' suffix in them. They all
are from tile pieces, just removing the b's from all the items works, but
tile pieces are really common and I assume this has not only broke mine, but
will break everyone's XML files people have shared.
Please let someone take a look at it.
|
Meanwhile there is no consistency...
Has the -b and 'with Groove' moniker removed, but [P=3068bpb0431,1]
has not. While the regular has...
|
We are still updating the 2 x 2 decorated tiles. There are over 2000 of them,
so it will take a while.
|
|
| Author: | Admin_Russell | | Posted: | Feb 15, 2024 14:39 | | Subject: | Re: Variants Thread - February 12 | | Viewed: | 276 times | | Topic: | Catalog | |
| In Catalog, Admin_Russell writes:
| | Hello again everyone,
Below I have listed the general groups of variants we are tackling and the results
of the deliberation over the last month. I was originally planning to provide
a schedule for when these changes will happen, but based on the progress with
the tiles since February 1, I am hesitant to commit to any timeline except that
we will not change anything on this list prior to February 15.
|
Today the catalog team got a message (in all caps) protesting the variant merges.
Some of the points have not been addressed yet, so I thought I would take this
opportunity to answer these before we get started with merging.
Sorry it's so long. 
01 WHY RUIN SOMETHING THAT WORKS SO WELL! YOU WILL LOSE MANY CUSTOMERS AROUND
THE WOURLD,
IN THIS HOBBY/WORK OF ART THE BUYER ALWAYS COMES FIRST!
One of the things people will learn about the BrickLink catalog is that it is
HUGE. Meaning that it would be hard to ruin it by just changing a few entries.
02 IF YOU DO THIS, YOU WILL DESTROY THE GREATEST REFERENCE FOR LEGO PARTS ANYWHERE
ON THE INTERNET, PEOPLE FROM AROUND THE WORLD HAVE BEEN DOING DATA ENTRIES FOR
20 YEARS, ALL THIS DATA WILL BE GONE!
We are actually saving the data, and others have done this too:
https://www.bricklink.com/message.asp?ID=1454780
In some cases we will be making Help Pages to preserve the most useful data.
03 THER IS NO NEED TO DO THIS IN THE FIRST PLACE BACUSE WHEN THERE IS 2 OR 3
VARIANTS THER IS ALWAS A PICTURE OF THE TOP AND BOTTOM OF EACH PART SHOWING THE
DIFFERENT DESIGN IMPROVEMENTS!
The need is both for sellers who have boxes of used parts to sort and buyers
who have to make their way around a catalog with entries that are hard to explain.
04 MANY OF US WILL USE CHINESE BASED WEB SITES AND OR BRICK-OWL.COM TO SOURCE
OUR PARTS!
I don't think so!
05 YOU ARE MAKING TO VERY BAD OF A DECISION WITH NOT IN PUT FROM THE US, AFOLS
/ BUYERS / SELLERS,
We took input from people for the last month in the Forum, plus other input for
many years. These decisions were not made in a vaccum.
06 DIFFERENT VARIANTS HAVE HAD SEPARATE ENTRIES FOR 20 YEARS, DONT "FIX"
WHAT IS NOT BROKEN OR YOU WILL HAVE THE SAME FATE AS SEARS
07 THIS DOES NOT HONOR DANIEL JEZEK, THE FOUNDER OF BRICK-LINK.COM IN ANY WAY!
For sure, Dan would have been on the side of this project. He sometimes referred
to the "balkanization" of the catalog as a bad things. Many of the variants
being removed would likely not have been approved under his leadership.
08 THIS RUNIS EVERTHING HE DID FOR AFOLS / BUYERS / SELLERS
IF HE WAS STILL ALIVE TODAY HE WOULD BE VERY DISAPPOINTED!
I think he would be relieved to not have to account for several different kinds
of hollow studs. In fact, he was the one that made the policy that only ONE head
stud variant would be used in all minfigure inventories. By continuing to allow
solid stud heads in early inventories, we are actually breaking this policy.
09/A IN JULY 2018 YOU INTRODUCED STUDIO WITCH IS IN INDISPENSABLE, STUDIO AND
BRICK LINK ARE LIKE SALT AND PEPPER OR PRIMER AND PAINT THEY MUST BE IN SYNCHRONIZATION
WITH EATCH OTHER
Agreed, although it is interesting that despite my personal efforts to further
integrate Studio into this Forum, both the administration and the Studio userbase
have insisted on keeping them separate.
09/B RIGHT NOW I CAN DESIGN A MOC ON STUDIO, I WILL THEN EXPORT THE PARTS TO
BRICK LINK AND ORDER THE PARTS, BUILD THE MOC, CREATE THE INSTRUCTIONS AND SELL
THEM ON REBRICKABLE.COM
Or you could do this in MOC shop next year (2025), but only if the MOC meets
certain standards.
09/C WHEN YOU MERGE VARIANTS YOU WILL RUIN BRICK LINK WEATHER YOU INTENDED TO
OR NOT! IF YOU DO THIS I WILL HAVE NO CHOSE BUT TO USE BRICK-OWL.COM FOR THE
MERGED VARIANTS
I'm not entirely sure whether Brick Owl will retain these variants after
we have merged them. I would advise against it, but if Brick Owl wants to corner
the market on parts that almost nobody wants, they are free to to that. The Brick
Owl catalog was decoupled from the BrickLink catalog years ago with the invention
of the Brick Owl ID (BOID).
09/D THE PROBLEM IS BRICK-OWL.COM IS NOT INTEGRATED INTO STUDIO, THAT MAKES ORDERING
PARTS A LOT MORE DIFFICULT, AND VERY TIME CONSUMING!
Well there is a reason that Studio is integrated with the BrickLink catalog and
not other catalogs. We pay for the development and maintenance of Studio, and
we choose to benefit our platform with the integration.
09/E I WILL HAVE TO MANUALY AND IVDVUALY LOOK FOR EACH PART ON BRICK-OWL.COM
THIS WILL TAKE HOURS!
My advice is keep using BrickLink. The variants we are removing aren't going
to make a lick of difference in a Studio model. I would welcome any real-life
cases where this variant merge project affects people's using of Studio.
10/A ALSO IF I BUY INSTRUCTIONS ON REBRICKABLE.COM AND BUY THE PARTS FROM BRICK-LINK.COM
THIS PROCESS SHOULD ONLY TAKE A FEW MINUTES FOR THE ALGORITHM TO PROSESS THE
DATA
Rebrickable is an affiliate of ours, and they are being briefed on all changes.
They Rebrickable folks are quite the experts at mapping things, so I wouldn't
worry about this too much.
10/B IT IS CRITICALLY IMPORTANT TO KNOW THE DIFFERENCE BETTWEEN SLOPED BRICKS
WITH A RORGH OR TEXTURED SURFACE AND SLOPED BRICKS WHITH A SMOOTH SURFACE
Sorry, it is not. There are not simply 2 kinds of textures. There are a range
of textures that are out there, and only showing 2 on BrickLink presents a false
dichotomy to our users.
10/C FOR EXAMPLE SLOPE BRICK 2 x 4 (45°) WITH ROUGH SURFACE 3037 IS MORE DESIRABLE
BECAUSE IT DOES NOT GET SCTRATED AS EASLY AS ONE WITH A SMOTH SURFACE
Yet currently on BrickLink (pre-merge) there is no way to order only a "rough
surface" slope. You could get any of a wide variety of textures, including
ones that some people think are smooth. There are a lot of blind partouts going
on out there, so don't think for a minute that every seller listing even
the smooth ones has actually looked at every brick, especially the New stock.
10/D https://img.brickowl.com/files/image_cache/larger/lego-red-slope-2-x-4-45-with-rough-surface-3037-32-935193-81.jpg
BrickLink Discussions Moderators, please leave this link as an exception. That
is indeed a beautiful image.
11/A IF YOU INTEGRATE BRICK-OWL.COM WITH STUDIO, IT WOULD MAKE THINGS EASER FOR
US AFOLS
The chance of that happening is very, very low - sorry.
11/B HOWHEVER THE NUMBER OF PARTS, NUMBER OF STORES AND THE SIZE STORES ARE FAR
GREATER ON BRICK-LINK.COM THAN ON BRICK-OWL.COM OR THEY MIGHT NOT HAVE THE PART
IN THE COLOR THAT I WANT SIMPLY BECAUSE THER ARE LESS AVABILE
Very true, and one of the reasons for that is the active catalog present on BrickLink.
People are attracted to the catalog, even though most variants the LEGO Group
releases never make in into the catalog.
12/A LET US THE SELLERS AND BUYERS DECIDE THROUGH A BINDING VOTE, WEATHER OR
NOT TO MERGE THE VARIANTS AFTER ALL IF THERE WAS NO DEMAND / BUYERS THER WOULD
BE NO REASION FOR THIS WEB-SITE TO EXIST IN THE FIRST PLACE
I've said this before, but if we left it up to a general user vote, BrickLink
would lose most of the variants in the catalog today.
12/B THAT MEANS THAT YOU WOULD HONOR THE VOTE AND PUBLISH THE NUMBERS FOR ALL
TO SEE!
We don't even publish the votes for Forum suggestions or BDP models. It would
increase transparency, but that may be too transparent.
13 THE PROBLEM IS BRICK OWL.COM IS NOT INTEGRATED WITH BRICK VALUT.TOYS
THAT COULD RUIN ONE OF THE BEST PLACES TO GET CUSTOM STAR WARS MOCS/SETS
Brick Owl and Brick Vault are their own sites with their own concerns.
14 PUT THE OLD MOULDS / VARIANTS ON A SEPREATE WEB SITE! LINKS INCLUDED
There are some great sites out there that document many variants that we don't
recognize on BrickLink. We have no issue with people building or using those
sites.
15 IF YOU DONT LIKE THIS IDEA, ASK US THE SELLERS AND BUYERS WHAT SHOULD BE DONE
TO SOLVE THIS PROBLEM! ALSO THER WAS NO PROBLEN IN THE FIRST PLACE,
We have been asking these questions for years. Every meeting, every convention,
every Forum thread. These changes have been a long time coming, and community
input was at the heart of the decision to move ahead.
16 ARE THE PART NUMBERS GOING CHANGE OR MERGE ON STUDIO?
Yes. Studio pulls these from the BrickLink catalog, so they will change. The
tiles have already changed.
|
|
| Author: | Admin_Russell | | Posted: | Feb 14, 2024 19:55 | | Subject: | Re: Store Inventory Description Changes | | Viewed: | 90 times | | Topic: | Technical Issues | |
| In Technical Issues, 1001bricks writes:
| | In Technical Issues, macebobo writes:
| | Recently a change was made to the UI that only impacts sellers who like to add
a little color to their listings.
When the UI updates, it escapes any valid html color to the exact same rgb equivalent
for some unknown reason, taking 10 of the already limited 255 characters.
Please go back to not altering perfectly valid html code.
|
Please re-allow people to voluntarily open BrickLink pages in an iFrame (broken
since 15 dec 2023).
Even more important, please implement a log of any user side change?
We DO know BrickLink is "AS IS".
But it may increase your Karma thing if you to be completely transparent with
us?
|
The iFrame and the HTML issues are intentional security related changes. In both
cases, we tried to minimaly disruptive.
|
|
| Author: | Admin_Russell | | Posted: | Feb 13, 2024 20:39 | | Subject: | Re: Variants Thread - February 12 | | Viewed: | 144 times | | Topic: | Catalog | |
| In Catalog, oukexergon writes:
| | In Catalog, Admin_Russell writes:
| |
Inside supports
We will merge 46212 (Brick 1 x 2 x 5) as planned
|
Can you please respond to the given rationales for why this should not happen?
These are very different parts (not variants) in connectivity, function even
within Lego instructions, and of course aesthetics where they have a specific
purpose in this case (usually used for transparency). Where else is this part
merged? Who would benefit from the loss of this unique part?
Can you comment on why this and not the 1x2x1 without inside supports would be
merged?
|
Because the transparent 3004 and 3065 both exist, so this is necessary to keep
them apart.
The 2454 and 46212 do not both exist in transparent colors:
[p=46212,12]
The only reason to keep them separate is to distinguish the early solid color
versions which had no side supports. But that is a minor consideration and practically
speaking there is no functional difference.
You would also be hard pressed to say that any of those early sets came ONLY
with the earliest version of the part. Both types are correct, and maybe there
were both types present in some copies.
As for people needing to place 1 x 1 round tiles inside the 46212, this only
happens with the transparent version.
|
|
| Author: | Admin_Russell | | Posted: | Feb 12, 2024 22:20 | | Subject: | Variants Thread - February 12 | | Viewed: | 610 times | | Topic: | Catalog | | Status: | Open | |
| Hello again everyone,
Below I have listed the general groups of variants we are tackling and the results
of the deliberation over the last month. I was originally planning to provide
a schedule for when these changes will happen, but based on the progress with
the tiles since February 1, I am hesitant to commit to any timeline except that
we will not change anything on this list prior to February 15.
Frosted bricks
These will be merged as planned, and a new Help Page is being written on this
topic.
Smooth slopes
These will be merged as planned, and a new Help Page is being written on this
topic.
Connections between studs
This whole class of variants will NOT be merged as part of this project. Complete
research needs to be done for the related 1 x 3 inverted slopes and the differing
angles, plus more work to understand how the 2 x 2 inverted slope relates to
these parts.
Sprue marks
The minifigure chair was the only one in this category and it will be merged
as planned.
Torsos with ribs
This whole class of variants will NOT be merged as part of this project. However,
we will rename these parts to remove the “ribs” depending on if we can get some
better photos. We will also place a moratorium on any new torsos distinguished
by underside ribs.
Inside supports
We will merge 46212 (Brick 1 x 2 x 5) as planned, but as part of this project
we will not be touching 32064c (Brick 1 x 2 with Axle Hole and Side Supports)
or 10247 (Plate Modified 2 x 2 with Pin Hole). More research needs to be done
in regards to the practical use cases of the parts and their actual use in LEGO
sets. As part of this project, however, we will also mark part 772 for deletion
(with a 3 month time frame before a merge), even though it wasn’t on the original
list. This variant likely does not even exist and it’s similar in class to the
46212.
X-shaped axle holes
These will be merged as planned.
Hinges with teeth
These will be merged as planned, and a new Help Page is being written on this
topic.
Duplo bricks with bottom tubes
These will be merged as planned.
Blocked and vented studs
These will be merged as planned, and a new Help Page is being written on this
topic.
Determined entries for very common parts
Update: We are well on our way through the decorated versions of 3 out of the
4 parts. Another 250 of these are scheduled to be changed on Tuesday (tomorrow).
|
|
| Author: | Admin_Russell | | Posted: | Feb 10, 2024 15:55 | | Subject: | Re: New policy on Forum sales posts | | Viewed: | 134 times | | Topic: | Administrative | |
| In Administrative, TorontoLego writes:
| | Hi,
I posted a sale yesterday and got a message alerting me to this message (below).
Sorry I had missed that. One of the things it says is: Bans will be lifted
immediately if the member contacts us and lets us know they agree to the new
policy.
I'm not sure if this applies to me (ie if there's now a ban); however,
I wanted to confirm that I have no been made aware of this new policy and agree
to abide by it.
Thanks and all the best,
Mike
(TorontoBricks)
|
If you can post in the Forum now, you are not banned. The ban feature is all
or nothing when it comes to different topics.
|
|
| Author: | Admin_Russell | | Posted: | Feb 10, 2024 02:34 | | Subject: | Re: Adding to the Problem | | Viewed: | 178 times | | Topic: | Catalog | |
| In Catalog, StormChaser writes:
| | Considering the recent displeasure of the community regarding variants, why is
BrickLink adding to the variant problem with new catalog entries like these?
Instead of wandering aimlessly with no plan whatsoever and still
no written guidelines for variants, it might be wiser for this website to employ
someone at a high level who is capable of crafting solid, long-term visions for
the future.
|
Recognizing molded vs printed is nothing new on BrickLink. And these are collectors'
items 100%. Furthermore, they present no problems in the inventory system.
The parts in the variant project are all mainstream parts and are primarily used
for building, not collecting. We'll get some rules up soon, but it's
pretty clear from the Help overview page what will NOT be distinguished in the
future on BrickLink:
https://www.bricklink.com/help.asp?helpID=2625
There definitely is a plan when it comes to drawing the line on variants, and
it's a long-term plan that takes into account future upgrades to the system.
We have been discussing these points for almost a year now with various groups,
including our catalog panel. Don't mistake our ability to modify a plan to
accommodate certain groups of users with the inability to make solid independent
decisions.
|
|
| Author: | Admin_Russell | | Posted: | Feb 8, 2024 11:59 | | Subject: | Re: Bricklink Transaction | | Viewed: | 98 times | | Topic: | Designer Program | |
| In Designer Program, Senna88 writes:
| | In Designer Program, Admin_Russell writes:
| | In Designer Program, Senna88 writes:
| | I have made purchase of a bricklink designer program set. The payment says pending
on paypal which is understandable but I have not received a confirmation email
nor has my lego account updated with the order. Is this normal for pre ordering?
|
Please contact LEGO Consumer and Shopper Engagement (CSE) for details about your
order.
|
Ok thanks. Do you have a link or an email?
|
https://www.lego.com/en-au/service
|
|
| Author: | Admin_Russell | | Posted: | Feb 8, 2024 11:39 | | Subject: | Re: Bricklink Transaction | | Viewed: | 73 times | | Topic: | Designer Program | |
| In Designer Program, Senna88 writes:
| | I have made purchase of a bricklink designer program set. The payment says pending
on paypal which is understandable but I have not received a confirmation email
nor has my lego account updated with the order. Is this normal for pre ordering?
|
Please contact LEGO Consumer and Shopper Engagement (CSE) for details about your
order.
|
|
| Author: | Admin_Russell | | Posted: | Feb 7, 2024 12:34 | | Subject: | Re: Orders | | Viewed: | 181 times | | Topic: | Designer Program | |
| In Designer Program, brickerking writes:
| | In Designer Program, Admin_Russell writes:
| | In Designer Program, brickerking writes:
| | It took weeks to reach halfway on the last BDP… This is an epic fail for BL and
consumers… epic payday for resellers.
|
That is not true. The last BDP round sold out completely in less than 24 hours.
Things are moving very fast this time too. If you want to get one of these sets,
you need to place the order now.
|
Memory must be failing me, sorry!
If these are all legit orders then congrats to your marketing team!
|
We actually boosted our server configuration WAY past what we ever thought we
would need. The site was flying fast yesterday with all that bandwidth.
But the demand for these sets is super high and it looks like they will be mostly
gone by the end of the morning. A good problem to have, but a problem nonetheless.
|
|
| Author: | Admin_Russell | | Posted: | Feb 7, 2024 12:25 | | Subject: | Re: Orders | | Viewed: | 132 times | | Topic: | Designer Program | |
| In Designer Program, brickerking writes:
| | It took weeks to reach halfway on the last BDP… This is an epic fail for BL and
consumers… epic payday for resellers.
|
That is not true. The last BDP round sold out completely in less than 24 hours.
Things are moving very fast this time too. If you want to get one of these sets,
you need to place the order now.
|
| Author: | Admin_Russell | | Posted: | Feb 3, 2024 01:04 | | Subject: | Re: Variants Thread - January 31 | | Viewed: | 130 times | | Topic: | Catalog | |
| In Catalog, tmtomh writes:
| | Thanks for this consolidated update - it's definitely helpful.
FYI, though, the image and link for issue #11 on the Overview page are both broken
because
of... the catalogue change that issue #11 of the Overview page is supposed to
be documenting.
|
Thanks for reporting. The broken link is now fixed.
|
| Author: | Admin_Russell | | Posted: | Feb 2, 2024 17:09 | | Subject: | Re: Comment from seller missing from invoices | | Viewed: | 101 times | | Topic: | Technical Issues | |
| In Technical Issues, QBricks writes:
| | I've sent a couple of invoices this morning (AU time) and both are missing
'comments from seller', which means buyers aren't getting payment
information.
My first one affected was sent at 19.54 BrickLink time. Anyone else having the
same problem?
Judy
|
We believe we have fixed this issue. Please let us know if the problem persists.
|
|
| Author: | Admin_Russell | | Posted: | Feb 1, 2024 17:32 | | Subject: | Re: Bricklink API - Update Store Inventory | | Viewed: | 250 times | | Topic: | Technical Issues | |
| In Technical Issues, BrickFreedom writes:
| | Hi
Have you made changes to the (Update Store Inventory -- PUT - /inventories/{inventory_id})
API request?
Previously you could call the API with the following parameters and would have
no issues:
['quantity' = '-2']
Now it's responding with:
["description":"String input must not be null","message":"PARAMETER_MISSING_OR_INVALID"]
Weirdly a couple of requests have completed successfully but most of the requests
are failing with the above error message. Can someone please advise what this
error is and if it's a bug that has been released into the API by accident?
|
We are closely monitoring the effects of changing the item number for 4 basic
parts earlier today. There have been reports that Brickstore is having issues
and now you are reporting about API.
Please take a look here for the 4 numbers that were changed:
https://www.bricklink.com/catalogReqList.asp?viewYear=&viewMonth=&viewGeDate=&q=&viewStatus=A&itemType=&viewAction=I
|
|
| Author: | Admin_Russell | | Posted: | Feb 1, 2024 13:36 | | Subject: | Re: Variants Thread - January 31 | | Viewed: | 178 times | | Topic: | Catalog | |
| In Catalog, macebobo writes:
I haven't fully addressed the video by R.R. Slugger yet, but I plan to in
the next day or two.
|
| Author: | Admin_Russell | | Posted: | Jan 31, 2024 20:22 | | Subject: | Re: Instructions for 910002 studgate | | Viewed: | 64 times | | Topic: | Help | |
| In Help, legomalego writes:
| | Is there a secret to downloading the instructions for this set?
I have tried many times and it always seems to reset just as the download is
almost complete.
Frustrating to say the least.
Does somebody have a better link?
Thanks
|
If you're having trouble dowloading the instructions, try the low resolution
version:
https://bdpinstructions.s3.amazonaws.com/910002_LowRes.pdf
|
|
| Author: | Admin_Russell | | Posted: | Jan 31, 2024 20:13 | | Subject: | Re: Variants Thread - January 31 | | Viewed: | 172 times | | Topic: | Catalog | |
| In Catalog, taxan writes:
Thank you for the input.
| | Determined Entries for Very Common Parts
You are aware that what you are doing here, by removing the "with Groove"
text you are creating a “undetermined type” entry. That thing BL have
been working for years to get ride of. People that com her to chop can no longer
be sure what type they will get. Many seller that is to lacy to determent what
version they have will use this entry.
|
You are correct that normally we try to remove undetermined entries, and we did
go through a long period of correcting inventories with this part. Officially
they may be undetermined again, but they will be like 3001 and 3001old. This
subset (umbrella) relationship works well for super basic parts like this where
we don't want to burden every user of the site with the "with groove"
text.
The main reason why these and other related parts are being treated as an exception
is because of how old the original versions of the parts are. Tiles without groove
were last produced 50 years ago. They are relatively rare now and are mostly
in the realm of the collector. I have heard that some builders like them, but
then they can buy them from the "a" entry.
| | Blocked and Vented Studs
Why are you destroying the database that so many AFOLs have been help building
for years.
Adding a note to the listing are not going to help especial when we talking 100
of thousand notes that have to added and when Search engine like “Easy Bye”
doesn't even show notes when you using it.
And with the listing gone nobody will know where to add those notes.
|
I'll address this below.
| | Smooth slopes
Try to add a sticker to a rouge surface.
|
How smooth does a slope have to be to be considered a smooth slope on BrickLink?
This is the main problem with these types of entries. Listings for sale are subjective,
and the inventory records are subjective too. Take a look at all the sets these
"smooth" slopes are in, and then look at the ones they are not in - from
the same years. The data is almost meaningless.
| | Sprue marks
Are the windows glass going to be rename/merged to ?
|
No, they are not mainstream parts.
| | When people are building MOCs they want them to look good. A sprue mark are for
the most part something the doesn't want.
|
Exactly. So why do we have a dedicated entry for the version people DON'T
want? Nobody seems to have an answer for that, but that is the current system.
My advice for builders is, if you don't like the sprue mark, buy new chairs.
If the sprue is a problem, sellers should mark the lot as deficient in some way,
just like you would handle a batch of a color that was a little off, or bricks
that were heavily used.
| | Torsos with ribs
Like people have been telling you if they wont the old Minifigur they don’t
want the new Torso, (and some of those Torso wont even survive a Leg assemble
from the wrong time period whiteout cracking).
|
We will likely keep the torsos in the catalog and rename them to not refer to
the ribs. The real problem we're up against is the unwillingness to have
enough separate minifigure entries to handle all the permutations of variants.
Currently, this is not a problem with the torsos. But it could be if we start
adding torsos based on the ribs alone.
And just for the record, here again, the "vintage" entry is the umbrella
entry. No one is guaranteed an original minifigure when they buy under that entry.
If something is truly original, the seller really should mention this in the
notes.
| | X-shaped axle holes
+ and x shaped axle hole often have different use.
+ shape are for better and stronger connection and x is mostly for easy connection
and removing.
|
I'm sure there is a slight difference in performance between the two types,
but after having tried the x shape for a while, LEGO engineers have abandoned
that shape of hole. Functionally, they are considered equivalent, and the only
reason we would continue to distinguish them is for cosmetic reasons. Only the
1 x 2 brick with axle hole can really claim a cosmetic difference, but since
the version of the part that people want is so common now, it's hard to justify
the time sellers must take to sort them. Where is the market for parts with x-shaped
holes? Even as a collector you would be hard pressed to say a set only came with
the x-shaped hole. Look at the inventory data we have.
| | Blocked and vented studs
And here we are again. I have been here so long that I remember that BL at one
point even had it in its TOS that forbid the user to add Minifigs heads with
one of those.
|
Thank you for remembering this! And what we are doing now is reverting to Dan's
original policy, with the exception being made for solid stud heads, because
solid stud vs hollow stud is something the catalog recognizes everywhere now.
When the Hollow Stud minifigure heads started to come out, I felt it was a risky
thing to start distinguishing them in the catalog, and I refused to split other
parts on similar grounds. This one has an "undetermined" hollow stud:
But when the vented stud came out (and apparently there are two versions of the
vented stud as well) things were stretched too far. Now we were putting notes
in minifigure inventories and then adding the loose minifigure head as an alternate
item in the set with no matching Match ID.
For a while the case was made that because these parts involved minifigures,
it was worth all the fuss to separate the parts. But on the other hand, there
was no willingness at all to make enough minifigure entries to handle the true
number of permutations that were coming in sets.
People have suggested adding alternate parts for minifigure inventories, but
that goes against Dan's original plan for the site. He could have added alternates
to those inventories, but he chose not to. The reason is that when selling a
minifigure, if 1 out of 4 parts is the wrong type, that is a major problem. This
is why we police the minifigure listings for missing items. We take down hundreds
of them every week.
If the type of hollow stud really mattered to people, we could split the minifigure
listings accordingly. But the fact is that most people don't care about which
version of hollow head, because most minifigures have headgear or hairpieces,
and the stud type was never meant to have any meaning beyond the technical workings
of molding plastic. That's why there are over 1000 minifigure heads that
are exactly the same print, but have a different stud type.
What matters more is the printing on the head. This is what we need to spend
our time cataloging and filling up Item Names with. If minifigures were an edge
case like Clikits, we wouldn't prevent exhaustive catalog efforts to represent
everything to such a degree of fineness.
However, minifigure parts populate the very largest categories on BrickLink and
they continue to grow at a wild pace. Minifigures are VERY popular, they are
VERY mainstream, and they cannot be encumbered by excessive mold variations.
Of course, it's not just minifigure heads that are affected by this. Categorically,
BrickLink is unrecognizing the different hollow stud types in all parts - hollow,
blocked open, vented thin and vented thick.
| | Those are imported time reference for the Minifigs.
|
Yes, but the time reference is skewed by an inventory system that is incomplete,
and it can be replaced by a simple chart in a Help page that shows the approximate
years these various heads appeared. The BrickLink system can tell you no different
and no better.
| | By doing this (and I think this it only the start) you are more or less killing
BrinkLink.
By destroying the database BL are removing many buyers reason to com here. They
need to go to other places to get the info they need and the going to buy what
they looking for there.
|
In previous threads I have likened this move to pruning a garden. If the gardener
knew that pruning would destroy the garden, they wouldn't do it.
| | You didn’t even send a mail about this to the most important group on BL The
Buyers.
Whiteout buyer there will be no reason for seller to be here and you get no fee
to pay for everything.
Go through with and i give the site max 5 years before its gone.
|
I'm not going to get into which group on BrickLink is most important. We're
doing this for the greater good, and that includes members from every different
group.
| | I think the best thing to do is cancel the whole ting for now and start working
on an umbrella entry that can have more than one sub entry. That way you can
still have the best database and lacy (seller that don’t want to take
there time to sort out different molds or don’t know how to) sellers can list
the way they want.
|
We may cancel a few of these variant merges, but I do believe most of them will
go through. And I am 100% behind any effort to give us better tools to handle
variants and the different audiences that we have. But these particular variants
I don't imagine will ever be handled by a separate system. They are just
too obscure. Most people wouldn't even know they exist without the BrickLink
entries.
|
|
| Author: | Admin_Russell | | Posted: | Jan 31, 2024 18:38 | | Subject: | Re: Variants Thread - January 31 | | Viewed: | 151 times | | Topic: | Catalog | |
| In Catalog, connie writes:
| | These vintage parts should all go into a vintage area on Bricklink. Put them
into a separate area. Should not be that hard to just move them.
connie
By the way, speaking of working on stuff that really doesn't need to be worked
on..........we were told a couple of years ago that once all the vat and sales
tax was added to the checkout that THEN they would fix it so that those with
a sales tax number would not have to pay the tax. Has this happened? NO!! Nothing
is more frustrating than having to pay tax on something bought internationally.
So stupid. This is more important to me than variation in parts being redone.
Connie
|
US sales tax exemption is a project currently underway in the Marketplace development
team. No promises as to when it will be deployed, but it is being worked on agressively
and will likely be the next tax-related feature released.
Catalog changes have very little to do with our technical resources. We use them
to pull data but usually not to implement changes, unless we lack tools for a
specific project.
We considered placing frosted bricks and smooth slopes in their own categories
away from mainstream parts, and that idea is still on the table. However, both
of those areas have serious issues and it is likely that we will not keep them.
But at the very least we will retain information about them in a couple of dedicated
Help articles.
|
|
|
| Author: | Admin_Russell | | Posted: | Jan 28, 2024 21:43 | | Subject: | Re: Variants Thread - January 26 | | Viewed: | 140 times | | Topic: | Catalog | |
| In Catalog, dsimpsonugcs writes:
| | | | There are some clear errors in your research data. You are counting the sales
of the standard variants of the bricks multiple times. For instance, there are
three frosted variants of 3005. For each of those variants you attribute 3911
sales of the standard variant. You should count the sales of each standard variant
only once, but in your spreadsheet, you do it three times. The total sales of
the standard variants should be 20184, not 38150. The ratio of sales is actually
closer to 9:1, not 17:1.
|
|
Ok, let's dive in.
| | TL;DR Definite errors in data presented by BL admin, likely much of the data
is bad too. Conclusions can't be trusted.
|
All of the data in my chart comes from the publicly available 6-month price guide.
You are welcome to use this data to produce your own statistics. I would be curious
to see if you come to any different overall conclusions about frosted bricks
as a result.
| | I may have misunderstood the comparison of sales of parts in the variant listings
vs. those in the standard listing. Are sales in the standard listing limited
to only those with descriptions of "frosted" or some such? If not, what
exactly was counted? And if so, what exactly was searched for when collecting
the data?
|
My chart is a comparison between the data in all frosted entries and the data
in the standard entries (e.g. Item No. 3010). Because the frosted bricks are
a subset of regular bricks, we are basically seeing how they fare on their own
vs. mixed together will regular bricks. Keep in mind that for some of these cases,
there is no "regular" version - or another way of saying it is, the regular
version and the frosted version are the same thing.
Because this is publicly available data, I did not search sellers' notes.
One of the drawbacks of our price guide is that value can change drastically
depending on what a seller types into that field. Some of the ones sold for a
penny, for example, could have been filler (junk) bricks, but the data is mixed
in with the rest.
| | I ask because if the search was just "frosted" then I suspect you are
overcounting quite substantially as you are counting different types of fruit.
Old transparent parts become less transparent over time and as such are described
as "frosted." These are properly listed in the standard listing as they
aren't variants. They are standard bricks with age related quality issues.
Variants are different due to manufacturing. A new one would look different
than a new standard brick. I searched some of the standard types for "frosted"
descriptions. Some of them are indeed for a variant (e.g. "frosted with
vertical lines" ), but most were not. Others were for mixed lots where there's
no way to know how many deviants might be included. Are the ones that aren't
actually variants being counted? They shouldn't be, but I suspect all of
these are being counted. Can you please clarify the criteria for inclusion in
the counts?
|
Everything is counted. It's a comparison between what gets sold under one
class of entries (frosted) vs. what gets sold under another class of entries
(regular/undetermined), and then of course filtered by the Transparent-Clear
color and "Used" as a condition. I also used the regular average, not
the quantity average.
| | The counts were already way off due to the incorrect double and triple counting
of sales from the standard listings I previously mentioned, but if the above
is also true, then they are much further off.
|
If you take a look at the data, you will see I divided the real numbers by 2
or 3 depending on how many variants will merge to a single regular entry. So
for the 3010, there are 3 frosted entries which map to a single regular entry.
The number of total used sales as of today is 1481 (see first image below), divided
by 3 is 494, a little higher than the 480 from the other day that you see in
my chart. Maybe the extra attention has motivated people to buy them!
| | Also, taking the average of the price ratios is an incorrect operation. You
can't take the average (arithmetic mean) of ratios. You have to take the
geomean. Quick math example! The inverse of a ratio of 4:1 (4) is 1:4 (0.25).
Logically the "average" of 4:1 and 1:4 should be 1 (geomean of 4 and
0.25), not 2.125 (arithmetic mean of 4 and 0.25). Please use the geomean as
the average you posted (2.12) is wrong and misleading. FYI, the geomean of the
provided data is 1.47. However, if the counts are wrong, that means the average
prices are also wrong, and thus the ratios, and finally the geomean are wrong
as well. Garbage in, garbage out.
|
2.12 is indeed the correct average of those numbers. I will concede that the
geometric mean is better at handling ratios and outliers in general (of which
there are several in this data that I did not remove), but the arithmetic mean
is calculated correctly.
And I calculated the geometric mean to be 1.47, which is the same figure you
have. It still proves the point that the prices are better under the standard
entries.
However, a much truer comparison can be shown by taking the entire sales volume
of both entry types and dividing them by the number of items sold. This will
give you the average price per part in each section, which by a quick estimate
(not getting today's data or using the quantity average prices) shows $0.10
per brick under the frosted entries and $0.12 per brick under the regular entries
(see second image below).
This is still an improvement, and together with the sales volume, it still shows
that it would be better for selling if everyone listed under the regular entries.
| | The research you've done and the data you've collected is being used
to make decisions, or at least provide evidence those decisions are based on
something real. The data, at least in this case, are highly suspect. The analysis
of that data definitely has errors. If you collected similar data for the other
proposed changes, I would guess they contain similar errors. It is improper
to draw conclusions given the current bad state of the data and its analysis.
Are you going to go back, correct the errors, and better validate the data?
|
Like I mentioned above, the public data is there for anyone to use. I would welcome
any differing research, especially when it comes to conclusions that can be drawn
as a result.
By the way, data used to make decisions internally is pulled internally and represents
a much truer and broader picture, although with the BrickLink price guide, it
really is only a guide because of all the irregularities it has to account for.
There are different taxes (some are included and some not), there are canceled
orders, problem orders, and variability due to notes. Like the inventory system,
the price guide is meant to be an indicator, not scientific proof. But it's
what we have, so we use it with a grain of salt.
|
|
|
| Author: | Admin_Russell | | Posted: | Jan 27, 2024 18:36 | | Subject: | Re: Variants Thread - January 26 | | Viewed: | 138 times | | Topic: | Catalog | |
| In Catalog, Tarkur writes:
| | Just thought of some extra speculative questions regarding this update.
|
Some excellent questions, thank you!
| | 1. So models in future designer programs will not be allowed to use any of the
following variants you are removing? So for example someone uses part 30389b
or 30389c with an axel through it for structural integrity of the model. Will
Bricklink in this case police them to remove this at the cost of stability or
the models apperance?
|
Designers for BDP must use bricks that are in the official building palette associated
with that round of the program. These are by definition only the newest versions
of the part. Questions of stability and part availability are handled case-by-case
by our BDP staff who take each model through several rounds of scrutiny.
| | 2. Will we see more updates of this type in the future? depending on the answer
bricklink may lose users in the future.
|
Probably nothing this big. If we get a checkbox system there would be further
large updates for sure, but they would be of a different nature.
| | 3. Will this diminish buyers ability to report issues with their orders in cases
where the seller didn't use the notes feature on a merged item?
|
No. Buyers can always bring any concern to us - but hopefully to the seller first.
We get very few complaints about variants, actually.
| | 5. How will this update affect buyers wanted lists? Will items in those lists
be merged or just deleted? Will buyers get a notice for changing their wanted
lists?
|
After the merges, when the buyer tries to use their wanted list, it will prompt
them to correct any duplicate lots they may have. No lot will be deleted. At
that point they may wish to make adjustments or simply consolidate their lists.
| | 6. What will happen to colors of parts that only exist for one variant?
|
They will appear in the resulting merged part. Images will transfer over - plus
the price guide, wanted lists, my collection, etc.
| | 7. Are you going to remove variants within stud.io as well after this change?
|
Studio does not recognize all variants anyway, but we will be giving them a list
of changes so they can update their indexes. I have a feeling it will simply
be a matter of changing a few Item Numbers. They might lose a few parts, but
I would be surprised.
|
|
| Author: | Admin_Russell | | Posted: | Jan 27, 2024 17:56 | | Subject: | Re: Variants Thread - January 26 | | Viewed: | 280 times | | Topic: | Catalog | |
| In Catalog, Admin_Russell writes:
| | So far I have seen two YouTube videos addressing this issue, and I'll post
in this new thread to respond directly (and completely) to what they are saying.
|
The two YouTube videos I have seen are these:
R.R. Slugger: There's a BAD Bricklink Update Coming...
https://www.youtube.com/watch?v=aGRxNX8Cg_o
DuckBricks: Why Would Bricklink Do This? Is Bricklink Stupid?
https://www.youtube.com/watch?v=sk47Wb18ibg
In this post I will address the second one:
I'll begin with a quote from Chris which he used as part of the introduction:
“I decided to take down every single one of my wall displays and actually
consolidate them to be a lot better, neater, tighter, and more concise to allow
myself to be able to put up even more stuff.”
What Chris is doing with his collection is, in a way, similar to what we are
doing with the BrickLink catalog.
I do actually agree with the overall sentiment from this video. However, there
are several points I would like to challenge:
Quote from the video: “from the beginning, the catalog has just been
continuing to grow and grow."
Not completely true. There have been major corrections like this in the past,
and we make minor corrections regularly. One of the things that is often missed
by the average BrickLink member is that we reject the overwhelming majority of
variants. That means that the BrickLink catalog only grows to the extent that
we let it grow, and there are considerable restraints even now on the number
of variants we will accept.
2 x 2 Hinge Brick – this is a merge between 30389c and 30389b. It does
not involve the hinge brick without axle hole 30389a.
[p=30389c]
* | | 30389b Hinge Brick 2 x 2 Locking with 1 Finger Vertical and Axle Hole
Parts: Hinge |
* | | 30389a Hinge Brick 2 x 2 Locking with 1 Finger Vertical without Axle Hole
Parts: Hinge |
While we are talking about this early brick that many of you are excited to distinguish,
I will point out that we are missing inventory information in 15 Sets and 1 Gear
Item:
https://www.bricklink.com/catalogItemIn.asp?P=30389&in=S
https://www.bricklink.com/catalogItemIn.asp?P=30389&in=G
The determined version is only in 10 sets currently. If this variant matters
to you, please help us fill out the data in the BrickLink inventory system.
A correction concerning the 2 x 2 hinge brick:
“As a correction to the video, it has become clear that one of the examples
I mentioned, the 2x2 brick with click joint, is NOT being consolidated when it
comes to axle hole versus no hole - just the specific molding type of axle hole.
However, all other examples mentioned are accurate, and from a database point
of view, I still stand by my original sentiments in the video that this change
ideally should not be happening.”
However, there are indeed issues with the other examples:
Click Hinges –The number of teeth does not affect the number of locking
positions. A lot of people think that when they see the distinction in the catalog,
but it’s actually not true. This misunderstanding is one reason we want to remove
this distinction. These are simply cosmetic differences on a part that is not
typically used for cosmetic purposes.
[p=50340]
1 x 4 Clear Bricks – The 1 x 4 frosted bricks will be merged with the
1 x 4 standard brick (3010), not the specialty brick without tubes underneath
(3066).
[p=3010f3]
Smooth Slopes – there was a comment in the video that the result of a
merge will be a “random hodgepodge” where buyers may receive slopes that don’t
match each other. But this is actually the condition of the marketplace now,
pre-merge.
The oldest slopes had a very heavy texture (see photo below), whereas newer ones
have much less texture. And in addition to the slopes that seemingly have no
texture, real-life listings contain everything in between.
The presence of “Smooth” entries in the catalog gives the illusion that there
are only two grades of texture, but the reality is that listings based on subjective
criteria will produce subjective results. In fact, I’m pretty sure that much
of the Smooth Slope data we see in the set inventories is also subjective depending
on the experience of the contributor.
Community Poll – We don’t base our decisions on polls because if we did,
the collector community on BrickLink would have their agenda completely wiped
out by the majority who don’t care about picky details. Instead, we appoint very
detail oriented admins who represent the collector community and they are the
ones making the calls on variants on a day-to-day basis.
Date - Feb 1 or Feb 15 – Feb 1 was the original date we were going to
begin changes, but due to delays with the list of changes and requests to extend
the time a little, we pushed the date to Feb 15. However, the name and number
changes to tiles and the 1 x 1 round brick will start on Feb 1. Since these are
not merges, they will not affect listings in the same way.
|
|
|
| Author: | Admin_Russell | | Posted: | Jan 27, 2024 17:10 | | Subject: | Re: Variants Thread - January 26 | | Viewed: | 138 times | | Topic: | Catalog | |
| In Catalog, Legorama writes:
| | So why has this project been touted as a "proposed change" (your words,
not mine) if it was always going to happen? Right from the jump, the initial
post on the forum received backlash to the proposal, and this was 2 weeks before
any intervention from YouTubers (who may have had some of their facts wrong).
Why has there been no sign of reassessment in the face of the overwhelmingly
negative response? You use phrases like "the variants we are merging as part
of this current project" as if to say there never was a proposal - it was
always a certainty.
Why feign community involvement if it was always going to be irrelevant to your
decision? And why the rush to push this through? It doesn't take an expert
to see that the community and the admin are not seeing eye to eye on this matter
at all.
|
It is billed as a proposed change because based on the reaction, the whole project
could be scrapped at any time. This is why we put the idea out in public, first
to the Forum, and then to the larger group of active sellers.
We are aware this is a "hard sell" situation. It is very difficult to
remove something from the catalog and have people happy about it. Consequently,
a lot of work was done in preparation for this project, to make sure just the
right entries were targeted and for the correct reasons.
What we are looking for in the responses are details we missed when doing research
and angles we had not thought about before. But personally I have not seen much
of that. Most of the responses from the email didn't really bring anything
to the conversation other than a general sentiment of "variants are important
- don't get rid of them" which by the way is a sentiment I also strongly
hold. But that's not what this conversation is about.
There are already several parts in the project that are currently on hold, and
they may not make it through. The wait time we have built into this project isn't
just to allow sellers to add notes if they wish. It's to give time for dialogue
and some exploration.
|
|
| Author: | Admin_Russell | | Posted: | Jan 27, 2024 16:35 | | Subject: | Re: Merging piece varian is a BIG PROBLEM | | Viewed: | 91 times | | Topic: | Catalog | |
| In Catalog, zorbanj writes:
| | It's not nearly as bad as it looks once you dig into the list.
I have 2 monitors. I opened the list on the right monitor and searched my inventory
on the left monitor. Did a copy and past from the list and used asterisks for
the searches. For example, for torsos with ribs I searched using "973p*"
and for the hinges I searched using "teeth". Then i just added the text
in each comments box I had ~ 175 lots and it took about 15 minutes. It's
easier if you use brickstore but I don't.
|
Thank you for sharing your experience!
|
|
| Author: | Admin_Russell | | Posted: | Jan 26, 2024 19:14 | | Subject: | Re: Variants Thread - January 26 | | Viewed: | 223 times | | Topic: | Catalog | |
| In Catalog, StormChaser writes:
| | In Catalog, Admin_Russell writes:
| | My initial post on this subject earlier this month has garnered almost 700 replies,
|
I would like an official response on why the website is choosing not to implement
the suggestion many have recommended for years. Many of us would like
to see a redesign of basic catalog functionality which allows everyone to be
served equally.
Selectable variants is a long-term solution which demonstrates there is a vision
for the future of this website and a care for all members. What are the difficulties
with implementing a visionary solution? Not enough money? Not enough staff?
Not enough vision at the top?
Looking forward to a quality response to this question which many of us have
asked.
|
We do have replatforming coming up soon and a better handling of variants is
definitely on the list of things we are looking to improve when it comes to core
catalog functionality.
Selectable variants (we have called this the Checkbox Solution internally) would
help in cases with medium level variants. We could implement this in both the
marketplace and the inventory system, at the very least.
However, there are many variants the catalog forces on the marketplace as a general
standard, and these are not optional. In the same way, there are many variants
that are so insignificant that BrickLink would never allow them to be distinguished
with a checkbox system.
So the answer is yes, in part.
But the variants we are merging as part of this current project would fall into
the last category. Maybe the "middle ground" could be expanded to include
them at some point, but from where I'm sitting now, I don't see that
happening.
|
|
| Author: | Admin_Russell | | Posted: | Jan 26, 2024 18:51 | | Subject: | Re: Variant merge - specific answers needed | | Viewed: | 98 times | | Topic: | Catalog | |
| In Catalog, SylvainLS writes:
| | In Catalog, Admin_Russell writes:
| | […]
Unfortunately the data linked to a catalog entry is dynamic in orders, so the
only thing that is recorded there is the number behind the number - the index
for that entry, which never changes.
So if a lot is purchased before the seller adds the note, the lot will show up
as a merged entry in the order if the catalog entry is merged.
|
Maybe it’s the hour (already tomorrow here ) but even with an idea of what
you’re trying to say, I’m not sure I understand.
So, an example:
1. Buyer orders variant A from store lot N and variant B from store lot M.
2. Seller doesn’t add the note.
3. Catalogue entries are merged.
4. Order shows two lines for the new part, from store lots N and M.
Right?
|
Yes.
|
|
| Author: | Admin_Russell | | Posted: | Jan 26, 2024 18:50 | | Subject: | Re: Variants Thread - January 26 | | Viewed: | 150 times | | Topic: | Catalog | |
| In Catalog, WoutR writes:
| | In Catalog, Admin_Russell writes:
| | And we’ve never been able to settle on
a reason for these peculiar markings. Some have suggested they are simply the
same patterns one would find on solid color bricks of the same era. Whatever
they are, though, this type of variant is typically found only in sellers’ notes
and not reflected in standalone BrickLink entries.
In fact, it is a peculiar thing that these entries were only for Transparent
versions of the part. We don’t really do that on BrickLink. Normally, all the
colors are placed under one entry.
|
The "frosted" appearance is caused by increased roughness of the inner
surface of the brick. During moulding, bricks can stick on the wrong half of
the mould when the mould opens and cause problems with the release of those parts.
The rough surface adds friction and helps to prevent that.
In some cases, moulds started out with a smooth surface and the inner surface
was modified during maintenance later. In other cases, moulds were made with
that rough inner surface from the start.
As far as I know, the frosting was included in the catalog only because of the
visual appearance. Smooth transparent bricks often look better.
Images:
- Two versions of 3001 brick with mould number 214-2
- Inner surface of a broken "brittle blue" brick.
Both these bricks would look "frosted" if they were transparent.
|
Thank you for contributing these details to the conversation! Do we have your
permission to use the images in a Help article?
|
|
| Author: | Admin_Russell | | Posted: | Jan 26, 2024 18:28 | | Subject: | Re: Variant merge - specific answers needed | | Viewed: | 95 times | | Topic: | Catalog | |
| In Catalog, jennnifer writes:
| | | | In Catalog, Admin_Russell writes:
|
Thanks for taking the time to answer these questions. It's good to have more
of the specifics.
| |
| | What happens 3 months from now when a seller who's been away reopens his
shop and doesn't understand what happened? You simply cannot count on every
single member receiving, reading, and understanding the email message sent out.
Will they receive any Action Items within BrickLink to understand the changes?
|
All sellers who had logged in in the last 6 months were notified by email. As
you may recall, originally a seller's inventory would be completely deleted
after 6 months of inactivity. Now it's not of course, but if they wait a
year, the whole account gets anonymized.
So relative to that, I would say this is not a monumental thing for people who
happen to be inactive for a while. It will probably mean they will need to consolidate
a few lots in their store.
|
The results may not be monumental, but they may not understand what's going
on. If they've missed the one announcement, they are going to find a bunch
of duplicate lots. It's going to seem to them that a bunch of items are 'missing'
when they go to look for a merged variant. There's going to be confusion
and then many, many questions here in the Forum. (See sales tax / onsite payment
threads for an example of how long a miscommunication can exist.)
I think there should be a visible notification in the My Actions List similar
to the ## Lots Marked for Deletion. It should be a log of: Lots Affected by Merged
Variants. Sellers should be able to click on it and see every affected lot in
their shop.
|
I wish we were at the place where we could deploy something like that for occasional
use. The best I believe we will have to offer is an XML list which we are still
working on.
| | | | | | I wonder how much Catalog Credit will just vanish on Feb 15th. Credit for images,
items, inventories, ... all gone.
|
Merges don't touch any of that stuff. It's all retained, but it may not
be retained in the same format as before. For example, inventory change requests
will still show in the logs and in the Forum messages. It's just that in
the logs, it may look like an item was changed to the same item. But the Forum
saves it just as it is, with all the comments and supporting documentation.
|
I expect to lose plenty of Catalog Credit. (I don't really mind, I was just
making a point.) I added many of these 3626b and c heads and their images over
the years.
Last thing that you may have missed when I reposted my original list of questions:
What's to happen to lots in active open orders when this change occurs? If
a seller doesn't choose to make a note on every affected lot, it's possible
a buyer will have ordered one specific variant that is merged by the time the
seller goes to pull the part.
|
Unfortunately the data linked to a catalog entry is dynamic in orders, so the
only thing that is recorded there is the number behind the number - the index
for that entry, which never changes.
So if a lot is purchased before the seller adds the note, the lot will show up
as a merged entry in the order if the catalog entry is merged.
|
|
| Author: | Admin_Russell | | Posted: | Jan 26, 2024 17:05 | | Subject: | Re: Variant merge - specific answers needed | | Viewed: | 96 times | | Topic: | Catalog | |
| In Catalog, Give.Me.A.Brick writes:
| | In Catalog, Admin_Russell writes:
| | In Catalog, jennnifer writes:
| | New question:
What's to happen to the number sequences of all the decorated parts?
|
They will need to be renumbered.
| | Do I understand correctly that
[p=3626b]
[p=3626c]
[p=28621]
are all to be one listing? Presumably 3626 something?
|
Yes, and yes.
| | Will the 210 Vented Stud heads currently in the catalog be renumbered into the
3626 series? Will there be a Change Log entry to document this change?
|
Yes. All "vented" and "blocked open" descriptors everywhere will
disappear. We will not distinguish them.
Even though it will take longer to run everything through the public change log
system, I will do it for the sake of transparency.
|
If I understand correctly, as of now, the 4 digits on 3626bpb**** and 3626cpb****
don't collide am I right? (Except when they are variants of the same head.)
So that would mean that the 4 digits will stay the same, which would be handy.
I mean:
3626cpb0909 will become 3626pb909 (3626bpb0909 doesn't exist)
3626cpb0912 and 3626bpb0912 will both merge into 3626pb0912
|
Yes, that is the idea. The aim is to be practical!
| | For the 28621pb**** the 4 digits will have to change, right?
|
We will need new numbers for them, just as if we had never distinguished them.
But all the old part numbers will be retained as alternates.
|
|
| Author: | Admin_Russell | | Posted: | Jan 26, 2024 15:53 | | Subject: | Re: Variant merge - specific answers needed | | Viewed: | 94 times | | Topic: | Catalog | |
| In Catalog, jennnifer writes:
| | New question:
What's to happen to the number sequences of all the decorated parts?
|
They will need to be renumbered.
| | Do I understand correctly that
[p=3626b]
[p=3626c]
[p=28621]
are all to be one listing? Presumably 3626 something?
|
Yes, and yes.
| | Will the 210 Vented Stud heads currently in the catalog be renumbered into the
3626 series? Will there be a Change Log entry to document this change?
|
Yes. All "vented" and "blocked open" descriptors everywhere will
disappear. We will not distinguish them.
Even though it will take longer to run everything through the public change log
system, I will do it for the sake of transparency.
|
Next Page: 5 More | 10 More | 25 More | 50 More | 100 More
|
)
)
)
)
