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.

EHT1880 tunes all linked

You are here

I finally got done adding the tune data (minimal, that is) to EHT1880, which is due back at the library today. A very interesting hymnal, and the Seattle Public Library's copy is in bad enough shape that I fear they may soon decide it's had it and get unceremoniously rid of it. I'm tempted to hold onto it and let it go to "Lost" status and pay the fine, just to keep it from being recycled.

But anyhow, now when I look at the hymnal page, I see a Hymnal Status line that I don't understand:

1 instance not published

see screenshot

What does this refer to?


Comments

The Hymn Status shows at a glance what is "published" and which authorities are connected, since it is possible for texts ant tunes to be "unpublished" while a hymnal is "published" and for hymnals to be "unpublished." Unpublished entities cannot be seen by people who are not editors, while editors can be blissfully unaware that something is not visible, since they can see everything.

In the EHT1880, one text was "unpublished" - #137B, which I found by "flipping" through the instances. It has now been published, which involves checking the Published checkbox.

But I couldn't figure out how or why one instance would have had the box unchecked, since I just got done completing the First Lines, adding lots of additional data, and plugging in all the tunes for that hymnal. I'm glad it wasn't something weirder!

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.