Create Subgroup

[Dov Feder]

I am a singer and have a rather large repertoire of songs. Is there a way to track all of my songs and then tag the songs I want to use for a particular set so those tagged songs appear in a subgroup I can then print out?

[Murdy]

Hi Dov,

What your asking for can be done very easily. Within the library, add an extra field for Boolean and ensure 'list entry' is selected from the 'where can we edit' option. You'd be best adding this to the entry status in the field function (this is optional).

Now within your library list view you can select which tracks you want byticking the check box, when you've made your selections, access the context menu, filter and select the boolean checked option, this will now only display your checked tracks.

I'm not at my pc for a few days or I would provide some screenshots but hopefully you'll be able to understand my instructions.

[Dov Feder]

Thanks for the reply Murdy.  I've been working on and off trying to get the database to function the way I want.  I wasn't really to understand your response - though it sounded simple.  However, just to make sure I explained the functionality I'm looking for correctly, I don't want to merely create a filter of songs but create a sustainable record of the songs I'm going to perform for that particular client.  So, out of 150 songs I may choose 8.  I want to be able to go back and review the 8 songs I played so when I perform there again I don't repeat the entire set.  When you get a chance I would embrace an opportunity to review your screenshots.  I think that will put everything into perspective.

Thanks again for taking the time to reply,

Dov

[Dough]

Dov - 

I think an easy design is a 4 library setup: Songs - Client- Event - Set

Song library is very stable after initial setup.  You'll add songs as you obtain them.  Song library lists all songs and any additional descriptive attributes that you like/need.

Client library may be fairly stable too if you have a lot of repeat customers. The Client library holds contact information and perhaps the client's likes and dislikes, etc.

Event Library has the event type, the date, time and duration of the event and descriptive attributes to the event.

Set library "pulls" these together listing the target event, the customer, and one song.  These 3 fields are all of field type "Link to entry".   I think you will need a song order field (type integer) within the set.  So if you have an 8 song set/event, in this library you will have 8 records which means you will select the event and customer 8 times to build all the records for this set in the example.  I like this option because the database flexes the correct size for your set.  (Set with 8 songs = 8 records in the library;  Set with 14 songs = 14 records in the library.  The tool is ready for your needs without modification)

Alternately.... you could have 10 song fields in the set record. This initially sounds much easier to do because you only select the event and client once.   However, I do not like this idea because the first client that wants you to play more than 10 songs will force you into adding more song fields to the Set library.

While this plan gets the database established and keeps the "sustainable record(s)" of a set/client/event, I suggest starting small using just the "must-have" fields before adding the descriptive fields. Get familiar with Memento display options using the "Field function" attribute for each field.  This is key to displaying the information you need later when reviewing past Events.  

I am quite new to this system and have been favorably impressed how it displays linked entry information.  If you employed the above design and opened the Client library, listed below each client is all Set(s) you built for that client.  Alternately if you opened the Song library, listed below a song is all the Set(s) it had been performed.  This is just the display function no filter needed.

I hope this discussion helps.  If it is beyond understanding, please forgive me.  Ask additional pointed questions and I'm sure someone with greater discussion skills will step in to help.  Perhaps I will try again too. 

[john cestuk]

I do this with
Members
Projects
Notes

I add my members once

I then add a new project for a member

Then ongoing I add notes as the project progresses. The project goes thru phases. Then, when I view a member I can see all the projects attached to that member. I can also see all the notes attached to a project when viewing a project.

Hope this helps. The point is you can see what songs you sang by creating a new project and then create notes for each project or gig.

I also do this to see what chores our family members have accomplished. I can view a chore of cleaning the kitchen. I can see which family member has cleaned the kitchen and when. I even assign points. I can view a chore and see all the history of which member has completed this chore historically. Or look at the family member to see what chores they have completed. Very flexible.