01-27-2025, 07:49 AM
Thanks for the replies, folks.
Yes, I'm quite adept at encoding multiple pieces of metadata into setlist names, etc:
But it's all a workaround for not having a better way to do it. And I don't have to explain to you the limitations of this. Most of us already know about problems like this, which is why we chose MobileSheets in the first place :-) It has flexible library management features.
For example; we don't "need" Collections, either. We could encode the genre and composer and book title into the "Song Name" of every song. But that makes for very limited filtering and sorting capabilities (and very clumsy looking song names). Much richer database experience to classify data entities into their own metadata categories.
Anyway, I've mentioned some use cases above for consideration :-)
Thanks!
Yes, I'm quite adept at encoding multiple pieces of metadata into setlist names, etc:
But it's all a workaround for not having a better way to do it. And I don't have to explain to you the limitations of this. Most of us already know about problems like this, which is why we chose MobileSheets in the first place :-) It has flexible library management features.
For example; we don't "need" Collections, either. We could encode the genre and composer and book title into the "Song Name" of every song. But that makes for very limited filtering and sorting capabilities (and very clumsy looking song names). Much richer database experience to classify data entities into their own metadata categories.
Anyway, I've mentioned some use cases above for consideration :-)
Thanks!