[jtoon86]

I have a few books that I'd like to store in Mobilesheets as the full book vs breaking out into songs. When I add the book to a set list, is it possible to (per set list) have it open to a specific page?

Use case is for psalm books. We play a different psalm per week -- (ie this week is on page 30, next week on page 32, etc..). As this spans over a 3 year time frame, I'd like to avoid having these all broken out as individual songs as I think this would be easier for building out each week's set list (basically we practice the song prior to the service, then I could simply bookmark/tag it so when I get to that piece in the set list, it will already be on that page).

Not the end of the world to simply enter a page number when I get to the piece and have it pull up, but thought I'd ask if this feature already exists. :-)  A few less touches on the tablet.

[BRX]

Not as far as I can see. Personally I think it's too special a use case and doesn't warrant more saving data per song and setlist into the database.
But if you practise and open the right pages beforehand anyway you could use the setting remember the last opened page in the settings. This works in/from setlists as well and opens the last viewed page of a song if you don't page forward to the next item in the setlist but go back from the song to the setlist screen and choose the next song from there.

[jtoon86]

Ok ... I came to the same conclusion as you, but figured I'd ask incase I was overlooking something. I'll probably end up breaking up the book as individual songs and associating each set list with the specific song for the week.

[Lawrie]

Ok ... I came to the same conclusion as you, but figured I'd ask incase I was overlooking something. I'll probably end up breaking up the book as individual songs and associating each set list with the specific song for the week.

This is how I approach this very problem (using the methodology that I believe is intended to be used in MS):

1. I create a csv file and import the csv into a collection (specified in the csv).  This collection is specific to the songbook*.
   
2. In the csv I specify the song number for inclusion in the "Custom" field.
   
3. As a result, all the songs in the songbook have an entry in the database, BUT there is only one pdf in use.  No messing around creating separate pdfs etc..
   
4. In MS Settings | Library Settings I have the Song title Formatting set to:
   %TITLE% %CUSTOM:[$(CUSTOM)]%This adds the contents of the Custom field to the displayed song title if it is not empty.
   
5. When I create a setlist, I simply specify that collection in the filters to limit choices and then add the required songs to the set list.  I can also search on name or number.
   

Voila! The set list entry picks the right song every time.
Takes a little longer to do the initial setup as the csv has to be created and imported, but this only needs to be done once, and you never have to search through a large pdf looking for a specific song again.


* I give the collection the same name as the songbook.  If the songbook is transposed for, say, trumpet, I will include the transposition in the name I give the pdf, and hence also the collection.

[IanMSpencer]

Ok ... I came to the same conclusion as you, but figured I'd ask incase I was overlooking something. I'll probably end up breaking up the book as individual songs and associating each set list with the specific song for the week.

If you can work out the spreadsheet programming, you might find that the import is easy enough not to fret - it's only bytes and it sounds like it is a long term, unchanging entry and the PDF will be shared.

If you can cut and paste the index into the spreadsheet, and calculate page numbers (are they single page, do they overlap, multi-page ending on a separate page from the next one where you can use the next entry) and format a from-to text field that MS will use. Use collections and or setlists to group the songs. If you check the CSV properly, you shouldn't have any maintenance to do in MS. 

I've got 1300 songs in my DB and it takes seconds to backup to the cloud (fast connection admittedly). 300 song entries will not overload the system and use of the collection, custom group fields and sensible naming can ensure that MS isn't an unmanageable mess.

[Geoff Bacon]

You may find someone has already uploaded a csv for psalm book

Geoff