08-29-2021, 12:13 PM
You would want to first go to Settings->Storage->Set MobileSheets Storage Location, set the storage location to your "Mobile Sheets Files" directory, then use Import->Batch Import to import the entire "Mobile Sheets Files" directory. On the batch import screen, you will see an option to "Populate Metadata from Directories". You will want to enable that if you already have your folders structured in such a way that fields in MobileSheets can be populated from them. You'll just need to specify the hierarchy you set up for the metadata (let me know if you have any questions about this). In case you are wondering why you have to first set the MobileSheets storage location, it's due to file permissions. MobileSheets can only access files under the default application data directory or under the storage location that is chosen. This is because MobileSheets is a UWP application (although with Microsoft not supporting UWP well, this could potentially change in the future).
I should mention that MobileSheets does not display data in the same way as a file system where there is support for an infinitely deep heirarchy of folders. Instead, you will have all of your songs/pieces on the songs/pieces tab, and then you can access songs by one of the group types if desired (such as artists, composers, etc). You can add filters to narrow the songs down more. Collections are often used for this purpose as well. As long as you can access your songs by using a group + any necessary filters, the app should work pretty seamlessly for you. Users who have very deep folder hierarchies and want to rely on those hierarchies run into issues with MobileSheets as it does not display the songs in that way. I purposely didn't want things to be structured like a file system because that's generally much slower and more tedious to access, especially when building things like setlists. I haven't ruled out trying to add some kind of file-like browser tab in the future, but the problem is that there isn't a one-to-one correlation between files and songs in MobileSheetsPro (songs can use multiple files all over the file system and files can be used by multiple songs), so that kind of throws a wrench into just showing files. Since each file can be tied to multiple songs, I would either need have to duplicate entries for each file that show it's tied to a song, or a way of grouping songs under a single file entry so that users can be aware of that.
Let me know if you have additional questions and I'll be happy to answer them.
Mike
I should mention that MobileSheets does not display data in the same way as a file system where there is support for an infinitely deep heirarchy of folders. Instead, you will have all of your songs/pieces on the songs/pieces tab, and then you can access songs by one of the group types if desired (such as artists, composers, etc). You can add filters to narrow the songs down more. Collections are often used for this purpose as well. As long as you can access your songs by using a group + any necessary filters, the app should work pretty seamlessly for you. Users who have very deep folder hierarchies and want to rely on those hierarchies run into issues with MobileSheets as it does not display the songs in that way. I purposely didn't want things to be structured like a file system because that's generally much slower and more tedious to access, especially when building things like setlists. I haven't ruled out trying to add some kind of file-like browser tab in the future, but the problem is that there isn't a one-to-one correlation between files and songs in MobileSheetsPro (songs can use multiple files all over the file system and files can be used by multiple songs), so that kind of throws a wrench into just showing files. Since each file can be tied to multiple songs, I would either need have to duplicate entries for each file that show it's tied to a song, or a way of grouping songs under a single file entry so that users can be aware of that.
Let me know if you have additional questions and I'll be happy to answer them.
Mike