Tune field ideas

[jwjacobson]

This thread will hold ideas for other fields to possibly add to tunes

[jwjacobson]

has_tag boolean would be True if a tune has a tag in its structure, (e.g., Star Eyes, East of the Sun) and default to false

[jwjacobson]

32_bars boolean would be True if a tune is 32 bars long. The other possibility is just to include number of bars as a field but that might be of limited utility

[bbelderbos]

So these will be derived fields (properties) or new database fields?

[jwjacobson]

New database fields, but I am not sure I want them yet, I just want a place to write them down so I don't forget

…

On Fri, Nov 24, 2023 at 9:54 AM Bob Belderbos ***@***.***> wrote: So these will be derived fields (properties) or new database fields? — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3YW23FGMIBRU5XH4BKVC2LYGCYJJAVCNFSM6AAAAAA7ZGS76WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRVG44DEOJXGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jwjacobson]

is_contrafact boolean, true if the tune is a contrafact. In which case there should be a second related field, contrafact_of, which points to the source tune if it's in the database or has a title string if not

[jwjacobson]

is_ballad boolean (default false), true if a tune is or is played as a ballad

[jwjacobson]

is_modal boolean (default false), true if a tune is modal

[jwjacobson]

tags (list of strings) (default None) this would be a useful way to hold lots of miscellaneous information about different tunes, including some of the booleans I've suggested here. it would also be more easy to implement in search than what I identified in issue 170