| Discussion Forum: Thread 137121 |
|
 |
| | | Author: | calsbricks  | | Posted: | Aug 7, 2012 02:08 | | Subject: | For consideration in the new Bricklink (when | | Viewed: | 203 times | | Topic: | Suggestions | | Status: | Open | | Vote: | [Yes|No] | |
|
| It would be very helpful if the Bricklink inventory allowed for a level above
category. For example there are several types of Bricks, e.g. arch, modified,
etc. These still remain as Bricks, however, the same as slopes, technic etc.
Having a level above current category e.g. Inventory family Bricks contains all
the categries/sub categories of bricks and so on.
This would be helpful for storage, reporting, searching etc. As I assume we are
sticking with a SQL backend for the new product, this isn't a major change to
the schema nor functionality - but it would certainly help us out
Anybody agree?
|
|
| | | | | |
| | | | | Author: | kzinti | | Posted: | Aug 7, 2012 02:23 | | Subject: | Re: For consideration in the new Bricklink (when | | Viewed: | 38 times | | Topic: | Suggestions | |
|
| In Suggestions, billduge writes:
| | It would be very helpful if the Bricklink inventory allowed for a level above
category. For example there are several types of Bricks, e.g. arch, modified,
etc. These still remain as Bricks, however, the same as slopes, technic etc.
Having a level above current category e.g. Inventory family Bricks contains all
the categries/sub categories of bricks and so on.
This would be helpful for storage, reporting, searching etc. As I assume we are
sticking with a SQL backend for the new product, this isn't a major change to
the schema nor functionality - but it would certainly help us out
Anybody agree?
|
There should probably be some sort of panel and surveys set up for discussion
on this. I know this isn't a Democracy, but it might provide very useful insight
for the next system. I'm sure a lot of the suggestions are being looked at, but
there are basic, fundamental things that could use tweaking to make it easier,
simpler.
|
|
|
| | | | | |
| | | | | Author: | Rob_and_Shelagh | | Posted: | Aug 7, 2012 02:40 | | Subject: | Re: For consideration in the new Bricklink (when | | Viewed: | 52 times | | Topic: | Suggestions | |
|
| In Suggestions, billduge writes:
| | It would be very helpful if the Bricklink inventory allowed for a level above
category. For example there are several types of Bricks, e.g. arch, modified,
etc. These still remain as Bricks, however, the same as slopes, technic etc.
Having a level above current category e.g. Inventory family Bricks contains all
the categries/sub categories of bricks and so on.
This would be helpful for storage, reporting, searching etc. As I assume we are
sticking with a SQL backend for the new product, this isn't a major change to
the schema nor functionality - but it would certainly help us out
Anybody agree?
|
Yes, IMO the redesign could really be broken down into 2 distinct areas. Firstly,
the layout, look, navigation of the site which uses the existing inventory databases
(I think this is what is being planned as Admin has stated the new site will
be developed in parallel to this site and launched in modules and then.. secondly
as you suggest a look at the structure of the inventory database itself and what
could be done to make it easier/quicker for those (who don't spend all day in
here and have years of site experience) to find what they want. E.g. the part
variant issue has become very complex and many buyers look for a part or have
it on their WL but miss a variant part when ordering from a store because they
are unaware of it. I think it might well involve significant changes to the databases
though, but still worth considering as this is only going to become more of an
issue over time as more parts are added.
Robert
|
|
|
| | | | | | | | | |
| | | | | | | Author: | PurpleDave | | Posted: | Aug 7, 2012 04:45 | | Subject: | Re: For consideration in the new Bricklink (when | | Viewed: | 43 times | | Topic: | Suggestions | |
|
| In Suggestions, Rob_and_Shelagh writes:
| | ...as you suggest a look at the structure of the inventory database itself and what
could be done to make it easier/quicker for those (who don't spend all day in
here and have years of site experience) to find what they want. E.g. the part
variant issue has become very complex and many buyers look for a part or have
it on their WL but miss a variant part when ordering from a store because they
are unaware of it.
|
I posted a suggestion recently where I'd like to see the Want List system changed
such that I can do a single WL entry that covers all variants of a single part.
Like if I put the Undetermined listing in my Want List, it will automatically
pull in any A/B/etc. variants on top of any listings that truly aren't sorted.
Being able to combine any two items into a single Want List entry might work
just as well, since then I'd be able to do a single search for either a torso
or any minifig that includes that torso.
|
|
|
| | | | | | | | | | | | | |
| | | | | | | | | Author: | jonwil | | Posted: | Aug 7, 2012 05:47 | | Subject: | Re: For consideration in the new Bricklink (when | | Viewed: | 33 times | | Topic: | Suggestions | |
|
| | | I posted a suggestion recently where I'd like to see the Want List system changed
such that I can do a single WL entry that covers all variants of a single part.
Like if I put the Undetermined listing in my Want List, it will automatically
pull in any A/B/etc. variants on top of any listings that truly aren't sorted.
Being able to combine any two items into a single Want List entry might work
just as well, since then I'd be able to do a single search for either a torso
or any minifig that includes that torso.
|
I would love to be able to say "show me all stores that have OR that have
any item listing in its inventory" (i.e. sets/minifigs/gear/etc that have
the part in it)
|
|
|
|
|
|
United Kingdom, England
USA, Missouri
Australia, Queensland