newVolunteer2
To be an effective volunteer, you need to understand a few things about how db.etree actually works. Database stuff. Ready?
At the core, db.etree is a database of setlists, or shows. Everything is organized by show, and the show is everything. Without shows, there would be nothing to add to your list. Without shows, there would be not way to add a SHN or FLAC source to your list, either. There would be no want list, or trading family, or any of the other features of db.etree. The show is the heart of db.etree.
The shows are numbered from 1 to over 300,000 at last count. Here's an example: http://db.etree.org/lookup_show.php?shows_key=16329. Each show in the shows database lists the artist, date, city, state, venue, and then the setlists and a place for a comment. Everyone who uses db.etree uses this information, whether they collect CDs, DATs, audio tapes, DVDs, or just want to look up the setlist. When you add a show to your list, you're really taking a snapshot of the master entry for the show, plus any other information you put on your list, like who you got the recording from or listening notes. That's why all of the information in the shows database should be generic -- no source info, no track lists, no song timings, no nothing except the names of the songs played and information specific to that particular performance. All of the other stuff goes in the notes on your list.
Why is it done this way? Because everyone has different recordings. Some folks have DATs, others CDs, others cassettes. Some recordings are complete, some are not. Some are audiences, others soundboards. The possibilities are endless. If *you* got a SHN recording from your buddy Bob, that has filler, that's tracked out a certain way, with two songs missing, I don't want that info on *my* list. My copy is different (I've got FLAC, no missing songs, etc., etc.). All of that information about *your* recording belongs on the notes section of *your* list -- NOT in the master entry in the shows database. If people had to add the same show again, each time the recording was a little different, the database would be full of duplicate shows, and that would suck.
The Golden Rule is that show entries are generic. Everyone can link to them and use them.
What happens when a band allows trading? Once someone has made a SHN or FLAC fileset of a particular recording, and if there is a volunteer for the artist, then the source entries come in.
There can be many sources for a single show. (Right? Of course!) So, creating a new SHN/FLAC source does not change the show entry. Instead, a new entry is made in the source database, that links back to the show entry for the performance. The source keeps track of the .txt file and the .md5 or .ffp files for the recording, and any comments that folks make about the recording. Here is the very first source entered at db.etree.org: http://db.etree.org/shninfo_detail.php?shnid=1 Please take a look.
If you move the mouse over the date of the show, you'll see that it's linked back to http://db.etree.org/lookup_show.php?shows_key=16329. You'll even see that there is another source for this show: http://db.etree.org/shninfo_detail.php?shnid=26145. That other source links back to the same show, #16329.
If you have this show, you can add it to your list with the extra info for source # 1, or the extra info for source # 26145, or without a source link, and with your own comments instead. It's up to you. The one thing you shouldn't do is change the show entry, just because you have a specific recording.
The critical idea here is that each performance results in a show that is generic, accurate and complete. Users who have a recording of a performance can add the show to their lists, and make whatever notes they want about it there. If the band is trader friendly, etc., you do the same thing. But, if there is a SHN/FLAC fileset in the source database, then anyyone can link the source to their list, which automatically puts the show there along with the source comments, users' comments, etc. Neato.
If you're a SetlistAdmin, please [newShowAdmin read this part next]. If you're a SourceAdmin, please read it too. Then, come back and read the special information about [newSourceAdmin sources].
At the core, db.etree is a database of setlists, or shows. Everything is organized by show, and the show is everything. Without shows, there would be nothing to add to your list. Without shows, there would be not way to add a SHN or FLAC source to your list, either. There would be no want list, or trading family, or any of the other features of db.etree. The show is the heart of db.etree.
The shows are numbered from 1 to over 300,000 at last count. Here's an example: http://db.etree.org/lookup_show.php?shows_key=16329. Each show in the shows database lists the artist, date, city, state, venue, and then the setlists and a place for a comment. Everyone who uses db.etree uses this information, whether they collect CDs, DATs, audio tapes, DVDs, or just want to look up the setlist. When you add a show to your list, you're really taking a snapshot of the master entry for the show, plus any other information you put on your list, like who you got the recording from or listening notes. That's why all of the information in the shows database should be generic -- no source info, no track lists, no song timings, no nothing except the names of the songs played and information specific to that particular performance. All of the other stuff goes in the notes on your list.
Why is it done this way? Because everyone has different recordings. Some folks have DATs, others CDs, others cassettes. Some recordings are complete, some are not. Some are audiences, others soundboards. The possibilities are endless. If *you* got a SHN recording from your buddy Bob, that has filler, that's tracked out a certain way, with two songs missing, I don't want that info on *my* list. My copy is different (I've got FLAC, no missing songs, etc., etc.). All of that information about *your* recording belongs on the notes section of *your* list -- NOT in the master entry in the shows database. If people had to add the same show again, each time the recording was a little different, the database would be full of duplicate shows, and that would suck.
The Golden Rule is that show entries are generic. Everyone can link to them and use them.
What happens when a band allows trading? Once someone has made a SHN or FLAC fileset of a particular recording, and if there is a volunteer for the artist, then the source entries come in.
There can be many sources for a single show. (Right? Of course!) So, creating a new SHN/FLAC source does not change the show entry. Instead, a new entry is made in the source database, that links back to the show entry for the performance. The source keeps track of the .txt file and the .md5 or .ffp files for the recording, and any comments that folks make about the recording. Here is the very first source entered at db.etree.org: http://db.etree.org/shninfo_detail.php?shnid=1 Please take a look.
If you move the mouse over the date of the show, you'll see that it's linked back to http://db.etree.org/lookup_show.php?shows_key=16329. You'll even see that there is another source for this show: http://db.etree.org/shninfo_detail.php?shnid=26145. That other source links back to the same show, #16329.
If you have this show, you can add it to your list with the extra info for source # 1, or the extra info for source # 26145, or without a source link, and with your own comments instead. It's up to you. The one thing you shouldn't do is change the show entry, just because you have a specific recording.
The critical idea here is that each performance results in a show that is generic, accurate and complete. Users who have a recording of a performance can add the show to their lists, and make whatever notes they want about it there. If the band is trader friendly, etc., you do the same thing. But, if there is a SHN/FLAC fileset in the source database, then anyyone can link the source to their list, which automatically puts the show there along with the source comments, users' comments, etc. Neato.
If you're a SetlistAdmin, please [newShowAdmin read this part next]. If you're a SourceAdmin, please read it too. Then, come back and read the special information about [newSourceAdmin sources].
Add Show
Index
Recent Changes
Preferences
Editing Tips
Edit this page
View page history