Open jessevondoom opened 13 years ago
so it would be a back end only notes space? would everyone be able to see everyone else's notes?
yes to back-end only, no to everyone seeing each others' notes. where venue data is essentially public data this would be treated more like contacts — totally private to the account, etc...
useful? too much? just thinking about tour spreadsheets i've seen and that's the part missing from the system now.
yeah after waking up I realized that of course not everyone's going to see your notes!
I think if you're gonna have a venue entry might as well have a place for notes. makes sense to me.
+1 to per-user venue notes
okay I've stared at this for a good 20 minutes. where do I go to make an issue? sorry!
Upper right hand corner of this page, under "Stats + Graphs" there is a button called "New Issue". No worries, everybody is a newbie at one point :)
You can also bookmark this URL: https://github.com/cashmusic/DIY/issues/new
Is there a place to keep advance info (booker contact, guarantee, merch deal, copy of the contract, etc.)? Rarely would I say the "venue" is where you want notes vs. the show, which includes things like booker, venue, promoter, sound person, attendance rundown, etc.
These all don't have to be indexed fields or anything, but having it in one place is beneficial. We've tried email, a google doc and now a shared calendar, but none of it is ideal. Being able to view it on our phones without having to sync calendars is key.
Apologies if this isn't the best ticket to comment on.
@ionrock Good point. That was my original thinking with venue notes, but I wasn't thinking so much about how nice it'd be to have all the promoter/sound stuff on a per-event basis. I don't even mind the idea of expanding the schema for events specifically — easy enough to have an "advanced" section that's internal/private and marked as such.
Top of my head for fields: Add to events:
Add to venue:
What do you think?
@ionrock And this is the perfect ticket for it. FYI: we've got universal tagging in the schema, plus we're adding a few PR-friendly fields to list management for similar reasons to this...so this kind of stuff will probably get a lot of focus after the initial launch of basic stuff.
What we've traditionally had on our advance info is the following:
A lot of this is the sort of info that ends up on a day sheet a tour manager might put up.
Obviously this is somewhat different depending on the type of show you are playing. I expect if you were an acoustic performer doing house shows your contact list will be different than a summer tour on a bus playing festivals.
One other thing I was going to bring up was organizing shows. I would presume you can mark events as part of a tour but can you also tag them as being part of some festival. We end up playing 10+ times for SXSW and send around our schedule to people, where I know other bands trying to do the same end up coming down as a part of a tour. It sounds like tagging should cover this, but it can't hurt to mention it.
hey eric - there is a comments box that you can put specific show info in. I used a version of this on the kill rock stars site and that's where i would make notes like early show, support, sxsw, etc
I actually didn't carry that over to the final platform — oversight more than intentional whiteout. So I think that's the core of the issue: putting back a private notes field (or fields) that'll let us do more proper internal planning. Don't want to make it too granular, but I think separating out contacts and show details, plus supporting tags, should do it...I'll open a proper ticket for that stuff next.
oh I see it on my admin. these are two different things we're taking about though. comments is in the admin and notes is not currently, right?
yeah i think we need to clarify terms...something like "public comments" and "private notes" so it's easy and clear that the comments will be listed with the dates, but that notes stay internal — or really anything similar. been so busy building the guts and i keep finding/fixing things like that, errors in design, etc...
show info and private notes?
Would it be worth adding a notes field to each venue on a per user basis? @maggiev23 might be the definitive answer here. Trying to make all venue data available to all users so it's semi-crowdsourced. I think the benefit there outweighs anything dumb like user errors or false corrections. But would an artist or tour manager find value in a notes field where they could store contact/booking info, notes on nearby food, whetever...