Seriously. Why is this taking so long? Shouldn't changes in new/popular sets
be a priority? The longer it waits, the more incorrect listings there will be.
I appreciate all that the catmins do, I really do. But when important change
requests get repeatedly left behind, maybe BL needs to actually hire some more
catalog staff.
Changes ARE getting looked at but we have no way of actually being able to easily
target more recent sets AND the year of release information is NOT included with
the change information that we see in our lists, we have to drill down for that.
Seriously. Why is this taking so long? Shouldn't changes in new/popular sets
be a priority? The longer it waits, the more incorrect listings there will be.
I appreciate all that the catmins do, I really do. But when important change
requests get repeatedly left behind, maybe BL needs to actually hire some more
catalog staff.
Ah, thanks for that. I hadn't seen that post. Still, it's pretty sad
that you still don't have that functionality. That seems more important for
an accurate catalog/listings than overhauling the Custom category...
As a side note, I'm curious. What is the process for approving a change request?
Is it just click-and-go, or does an admin have to possess the set in question
to verify? What happens when the corresponding discussion posting is purged before
the change request is dealt with?
Changes ARE getting looked at but we have no way of actually being able to easily
target more recent sets AND the year of release information is NOT included with
the change information that we see in our lists, we have to drill down for that.
Seriously. Why is this taking so long? Shouldn't changes in new/popular sets
be a priority? The longer it waits, the more incorrect listings there will be.
I appreciate all that the catmins do, I really do. But when important change
requests get repeatedly left behind, maybe BL needs to actually hire some more
catalog staff.
Austria, Wien
USA, Ohio
United Kingdom, England