LDraw.org Discussion Forums

Full Version: Parts Requestor System Requirements
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Yes - let's collect requirements here. Then I can build a web interface as part of the Parts Tracker. It should be linked to the Parts Tracker to facilitate automatic removal when an unofficial version gets submitted. There is Parts Tracker functionality that can be re-purposed for this.

Questions:
- Should each user have a limit on how many parts than can have on their "I request this" list?
- Should each user have a limited number of "I support this votes"?
- Should there be a hierarchy of votes (Urgent/Important/Useful/Nice to have)

LDraw Parts Request System Requirements:
- page listing requested parts (sortable by part number, description, vote tally), linking to
- page for each requested part, containing
- link to part image (peeron/Bricklink/personal URL)
- username of requestor
- usernames of supporters
- username of volunteer author
- comments/activity log (like on the Parts Tracker)
- links for "I support this", "I am authoring this", "Comment"

- page listing (for current user) of requested and supported parts

- admin functionality to edit/rename/delete entries

Chris
Chris Dee Wrote:
-------------------------------------------------------
> Questions:
> - Should each user have a limit on how many parts
> than can have on their "I request this" list?
> - Should each user have a limited number of "I
> support this votes"?

I don't see a good reason to limit either of these. If someone get out of hand we can just politely ask them to stop.

> - Should there be a hierarchy of votes
> (Urgent/Important/Useful/Nice to have)

I'm neutral on this.

> LDraw Parts Request System Requirements:
> - page listing requested parts (sortable by part
> number, description, vote tally), linking to
> - page for each requested part, containing
> - link to part image
> (peeron/Bricklink/personal URL)
> - username of requestor
> - usernames of supporters
> - username of volunteer author
> - comments/activity log (like on the Parts
> Tracker)
> - links for "I support this", "I am authoring
> this", "Comment"
>
> - page listing (for current user) of requested and
> supported parts
>
> - admin functionality to edit/rename/delete
> entries

All this looks good and I can't think of anything to add.
Chris Dee Wrote:
-------------------------------------------------------
> Questions:
> - Should each user have a limit on how many parts
> than can have on their "I request this" list?
> - Should each user have a limited number of "I
> support this votes"?

No, it's a wishlist with no obligation.

> - Should there be a hierarchy of votes
> (Urgent/Important/Useful/Nice to have)

No opinion but why not. On the otherside: Light is beautiful.

> LDraw Parts Request System Requirements:
> - page listing requested parts (sortable by part
> number, description, vote tally), linking to
> - page for each requested part, containing
> - link to part image
> (peeron/Bricklink/personal URL)
> - username of requestor
> - usernames of supporters
> - username of volunteer author
> - comments/activity log (like on the Parts
> Tracker)
> - links for "I support this", "I am authoring
> this", "Comment"
>
> - page listing (for current user) of requested and
> supported parts
>
> - admin functionality to edit/rename/delete
> entries

Wow! If it is doable why not. Important thing is that is going up fast. Additions can be made later.

w.
Chris,

is this in the made? How long it will take to go live? I'm questioning this 'cos there are continuously popping up part request and we have to rule them somehow. If building will take I'd propose to post the simple system and work with it 'til the PRS is in place.

w.
It would be good to get input on the requirements from the other SteerCo members. Kevin? Scott?

It has not got beyond the design stage yet.

Is this more important that a web submission interface for the OMR?

Chris
My opinion is to do what you are most interested in doing first. I'd prefer the Parts Requester System, but if I were you, I'd do what I want most.

Scott
Chris Dee Wrote:
-------------------------------------------------------
> Is this more important that a web submission
> interface for the OMR?

No. BTW looks like we have to kick some asses around.

w.
This topic is now moved for general discussion
Thanks for publishing this.

Here's my small opinion on this:

> Should each user have a limit on how many parts than can have on their "I request this" list?
> Should each user have a limited number of "I support this votes"?

I think: "yes, there should be a limit", because I fear 2 negative effects otherwise:
(a) unequality: a user posting 100 "want" votes will more probably get his part through than a user who just needs 1 part.
(b) loss of focus: spilling out just many "want" votes will not focus us onto the parts really needed.
Would we limit the number of "want" votes to, say, 10, then the users themselves will see
that workforce is limited, and that they cannot demand just tons of parts.
Instead, they have to decide which 10 ones are the most urgent ones,
and after these parts have been created, they can place them again.
For the reason of (a), I also ask that a user might place his 10 votes all on one part he needs very urgently,
or distribute them otherwise, like, say 5+2+2+1.

> Should there be a hierarchy of votes (Urgent/Important/Useful/Nice to have)

I think that would make things just complicated and difficult to track.
I wouldn't need that.

> LDraw Parts Request System Requirements

My suggestion would be: keep things as simple as possible.

> - page listing requested parts (sortable by part number, description, vote tally), linking to
> - page for each requested part, containing
> - link to part image (peeron/Bricklink/personal URL)
> - username of requestor
> - usernames of supporters
> - username of volunteer author
> - comments/activity log (like on the Parts Tracker)
> - links for "I support this", "I am authoring this", "Comment"
> - page listing (for current user) of requested and supported parts
>- admin functionality to edit/rename/delete entries

This would be the "gold" implementation, and if it could be done, of course be well appreciated here.
For me, much less already would suffice, for example a Wiki table where people can edit collectively
their requests. A simple script could check that no one places more than his allowed number of votes.
People could simply enter their vote count into a table cell.
However, that of course would be an intermediary solution until the "gold" one is possible.
I just fear that the "gold" one takes quite an amount of work.
Or can some structures from the existing PT be copied+pasted?
For example, the "wish" list in fact is very similar to the "parts" list,
and the "wish" activity is very similar to the "PT activity",
and the "wish status" is very similar to the "part status" etc.pp.

Would I get asked if this more needed than a OMR, then I personally would answer "yes".

best,
Steffen
I agree with Steffen, a limit on number of support votes would be great to avoid flooding, and make really needed parts stand up. But how do users refill their votes quota? After some time? Or do they get back votes they cast on a part when this part is done?
Pages: 1 2