Include stanza order in song session records

[OsakaWebbie]

I can't just add a Stanza column to the usage table, because the number/order of stanzas might change and throw off previously recorded stanza usage records. So the current thought is to add table "stanza" with an auto-incremented ID field. This would also allow stanzas to have a "type", so that indentation of choruses and such could be programmable.

• StanzaID
• StanzaType ("i": intro, "v": verse, "p": pre-chorus, "c": chorus, "b": bridge, "e": ending, "": other)
• SongID
• Order

Usage table would then have StanzaID added to it.

Affected files would include:

• song: add join to assemble lyrics display
• edit: multiple text areas for stanzas, with type selection
• do_edit: properly insert into both song and stanza tables
• use_chart: provide modal popup to reveal stanza detail; also allow call to pdfformat with stanzas of that session
• pdfformat: join stanzas, and add ability to save stanza info in usage table (this would become the primary place where users would save song sessions); confirm replacement if exists for that date, even if previously only SongID
• pdfgenerate: receive StanzaID instead of SongID+letter, and build TeX code from that
• (probably several others)

[OsakaWebbie]

Idea for how to denote stanza type in data: [s=v1] (or [S-V1] - capitalization should not matter) on either the first line of the stanza or, more logically, the previous line by itself.

The biggest challenge of this upgrade, by far, is the interface - stanza type, chords, and romaji designation (all the stuff in [brackets]) need a more user-friendly way of entering, and that's a lot of clever Javascript that doesn't yet exist.