You help make Hymnary.org possible. More than 10 million people from 200+ countries found hymns, liturgical resources and encouragement on Hymnary.org in 2025, including you. Every visit affirms the global impact of this ministry.

If Hymnary has been meaningful to you this year, would you take a moment today to help sustain it? A gift of any size—paired with a note of encouragement if you wish—directly supports the server costs, research work and curation that keep this resource freely available to the world.

Give securely online today, or mail a check to:
Hymnary.org
Calvin University
3201 Burton Street SE
Grand Rapids, MI 49546

Thank you for your partnership, and may the hope of Advent fill your heart.

Data Fields

You are here

This wiki page is a very good idea, however it has not been updated since it was created 3½ years ago. When I download a current spreadsheet, I am confronted by a number of Data fields that are not mentioned in the Wiki (nor anywhere else that I have seen). It is not clear whether they are things I am expected, or allowed, or denied the right, to fill in when entering a hymnal, nor is it clear, if I am allowed to do so, what the content ought to look like, be, and do. Just from the Page worksheet, here are the fields I see that I don't understand:

Hymn License ID
Text About
Text dnahID
Text Group
Tune Lilypond
Tune About
Tune Group

Are any of these things I should be entering if known? I do wish I knew Lilypond better, would like to be able to typeset my own hymnals... ;-)


Comments

These are data fields that could be included in a hymnal so they are included on the spreadsheet if you download the hymnal information as a spreadsheet. They are in the category of optional fields. They do not appear on the blank spreadsheets that you download from the wiki which contains the required and recommended fields. You are not expected to fill them in.

I'd still like to know what would be appropriate to enter in them, so I'll know what to do if I face a hymnal with that sort of info in it. I imagine (if I knew enough Lilypond) that I could use that field to enable folks to generate their own pdf's in cases where CCEL or TCH hadn't provided one. In particular I would be interested in the licensing one, I think, as I am guessing it may provide a way in some cases to make visible what copyright law would otherwise force to remain hidden. But I don't know. I'm guessing "dnahID" is something that is filled in by the machine (the way checking "published" generates a whole column of little "p"'s).

It looks like you are using an ad-blocker. Ad revenue helps keep us running. Please consider white-listing Hymnary.org or getting Hymnary Pro to eliminate ads entirely and help support Hymnary.org.