Go Back   vb.org Archive > Community Discussions > Modification Requests/Questions (Unpaid)
FAQ Community Calendar Today's Posts Search

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #1  
Old 12-15-2005, 11:00 PM
trashtreasury trashtreasury is offline
 
Join Date: Nov 2005
Posts: 2
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default Blanks and Postage Request System

I run http://www.trashtreasury.com, an Elliott Smith download hub and forum. I have a project I'm planning that will bring in a lot of traffic, without using a lot of bandwidth, but I need a tool built for me to make it an easy process:

Here's what I want to do and what I need:

One of my top long term goals is to archive every available audio performance at the LMA (Live Music Archive, a part of the Internet Archive, located at archive.org). Once the shows are there, it makes distribution much easier, and frees up my bandwidth for things that don't fall under their umbrella.

Unfortunately, even with the archive pipe, which for our purposes is as good as unlimited, there are still lots of people out there who don't have broadband, and simply can't access the lossless recordings. And, there's a good chunk of those who end up turning to the pirates on eBay to get their fix.

Now, another common way to get shows in the trading community is B+P (Blanks and Postage; I send you blank CD's with a SASE and you send me shows). I don't mind filling these requests, but I don't want it to be a major part of my life.

My thought is that I can build a team of people with CD's burners and broadband (I'm thinking at least 20-30 in the initial rollout, and adding more later if there's as much demand as I think there will eventually be), who can download shows from the archive, burn them and send them back.


Here's where the hack comes in. You knew I'd get to it eventually, right? What I need is this:

First of all, I want all my burners to be board members. Ideally, they could have an section right in the User CP where, once I had authorized them as team members, they will be able to enter their contact information (name, address, contact email if different than the one registered with) and contact preferences (Email, PM or both) and whether their contact info should be sent directly to the requester or whether they need an option to approve/deny the request.

The requesters will also be required to register for the board. Each show page on the content section of the site will have a link to "Request a B+P." If they are logged in, it will take them directly to the form; otherwise it will take them to a registration/login page. The form itself will automatically populate the show that they linked from, ask them for their name and contact info (so that it's available to the burner in case it's not legible when they receive it from the requester), and submit a request to the top person in the database, who will then be shuffled to the bottom of the list. If they have chosen to automatically accept all requests, their name and address will be PMed/emailed to the requester who can then send their B+P on it's way. If the burner is set to manual authorization, and the request goes unanswered for 48 hours, or the burner denies the request, it will be bumped to the next person on the list.

If a burner denies more than 3 requests in a row, they will temporarially be suspended, and I will take it up with them; this process doesn't need to be automatic, but the system should generate an email/PM to me regarding this if it's not. (This is not a vital feature)

The requests should stay in a queue for the burner, and they will have the ability to mark them done once they have been done. Once the burner has marked this completed (actually sent the mail is the goal), a pm/email will be sent to the requester, letting them know and giving them an option to send any feedback if the materials do not arrive or are damaged on arrival. (If they haven't been done because there is not enough postage or insufficient media, the burner can mark the request incompletable, which will notify me and the requester, and we'll work something out. If it's a postage issue, I will probably end up covering that out of my pocket, but I'm certainly not going to say that up front).

Last, but not least, of course I want it to keep records of all trades, and a database of contact info for all involved users.


I think I've hit all the high points. Let me know what you think, or if you have any questions. I know I've described the hack with a very narrow application, but I think this is something that could be customized for various types of trading on other forums as well. Heck, perhaps something is already out there that could be customized for this use...

Edit: Oh, one more thing. When a requester submits a request, they should receive clear instructions as to exactly what is required of them (i.e. include postage, include address, include sufficient blank media and make sure that media is mailed in a protective case to prevent damage).
Reply With Quote
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 02:11 AM.


Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2024, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.03062 seconds
  • Memory Usage 2,256KB
  • Queries Executed 12 (?)
More Information
Template Usage:
  • (1)SHOWTHREAD
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)ad_showthread_beforeqr
  • (1)footer
  • (1)forumjump
  • (1)forumrules
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (1)navbar
  • (3)navbar_link
  • (120)option
  • (1)post_thanks_box
  • (1)post_thanks_button
  • (1)post_thanks_javascript
  • (1)post_thanks_navbar_search
  • (1)post_thanks_postbit_info
  • (1)postbit
  • (1)postbit_onlinestatus
  • (1)postbit_wrapper
  • (1)showthread_list
  • (1)spacer_close
  • (1)spacer_open
  • (1)tagbit_wrapper 

Phrase Groups Available:
  • global
  • inlinemod
  • postbit
  • posting
  • reputationlevel
  • showthread
Included Files:
  • ./showthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/functions_bigthree.php
  • ./includes/class_postbit.php
  • ./includes/class_bbcode.php
  • ./includes/functions_reputation.php
  • ./includes/functions_threadedmode.php
  • ./includes/functions_post_thanks.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_postinfo_query
  • fetch_postinfo
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • showthread_start
  • showthread_getinfo
  • forumjump
  • showthread_post_start
  • showthread_query_postids_threaded
  • showthread_threaded_construct_link
  • showthread_query
  • bbcode_fetch_tags
  • bbcode_create
  • showthread_postbit_create
  • postbit_factory
  • postbit_display_start
  • post_thanks_function_post_thanks_off_start
  • post_thanks_function_post_thanks_off_end
  • post_thanks_function_fetch_thanks_start
  • post_thanks_function_fetch_thanks_end
  • post_thanks_function_thanked_already_start
  • post_thanks_function_thanked_already_end
  • fetch_musername
  • postbit_imicons
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • postbit_display_complete
  • post_thanks_function_can_thank_this_post_start
  • tag_fetchbit_complete
  • forumrules
  • navbits
  • navbits_complete
  • showthread_complete