<div dir="ltr">It seems so far we'll go with the original idea of relabeling the page headings to match the menu links.<div><br></div><div>I can get started on a working branch soon. Thanks, everyone, for your contribution to the discussion!</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 17, 2024 at 3:33 PM Cerninakova Eva via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org">evergreen-general@list.evergreen-ils.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I agree with the reasons Jeniffer said. In addition, it seems to me better in terms of translations as well: when generated automatically, some currently used headers are problematic if they are composed of several parts (the union of two terms may not always be a suitable translation of the interface name).<div><br></div><div>Eva<br><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">st 17. 1. 2024 v 20:24 odesílatel Terran McCanna via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>> napsal:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">+1 to what Galen said.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 17, 2024 at 2:20 PM Galen Charlton via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>Hi,</div><div><br></div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 17, 2024 at 1:34 PM Jennifer Pringle via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div lang="EN-CA">
<div>
<p class="MsoNormal"><span style="font-size:11pt">I actually think we should use the names from the menus rather than the current headings on the pages. It sounds like it will be more work but, at least for us, those are the names
library staff know the interfaces by and in most cases the names the interfaces have had for years. Changing them to match the headings will also change the order of the menu and in come cases split up interfaces that are currently nicely grouped together.
</span></p></div></div></div></blockquote><div><br></div><div>I agree with the idea of making the headers of the individual pages match the names from the menus / landing page links. While thought should also be given to updating the IDL names of the tables, I generally am biased towards using human-chosen labels for all interfaces and, in the long run, leaning rather less on the automatically generated admin pages. <br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div lang="EN-CA"><div><p class="MsoNormal"><span style="font-size:11pt">(and will add the word Configuration to almost every menu item on the Server Admin menu)<u></u><u></u></span></p>
</div></div></div></blockquote></div><div><span class="gmail_signature_prefix"><br></span></div><div><span class="gmail_signature_prefix">I'm mildly against the idea of adding "Configuration" to every page link - it's implicit for nearly all of them.<br></span></div><div><span class="gmail_signature_prefix"><br></span></div><div><span class="gmail_signature_prefix">Regards,</span></div><div><span class="gmail_signature_prefix"><br></span></div><div><span class="gmail_signature_prefix">Galen<br></span></div><div><span class="gmail_signature_prefix">-- </span></div><div dir="ltr" class="gmail_signature"><div dir="ltr">Galen Charlton<br>Implementation and IT Manager<br>Equinox Open Library Initiative<br><a href="mailto:gmc@equinoxOLI.org" target="_blank">gmc@equinoxOLI.org</a><br><a href="https://www.equinoxOLI.org" target="_blank">https://www.equinoxOLI.org</a> <br>phone: 877-OPEN-ILS (673-6457)<br>direct: 770-709-5581<br><a href="http://evergreen-ils.org" target="_blank"></a></div></div></div>
_______________________________________________<br>
Evergreen-general mailing list<br>
<a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
</blockquote></div>
_______________________________________________<br>
Evergreen-general mailing list<br>
<a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
</blockquote></div></div>
_______________________________________________<br>
Evergreen-general mailing list<br>
<a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr">Gina Monti (she/her)<div><div>Evergreen Systems Manager</div><div>Bibliomation, Inc.</div><div>(203) 577-4070 ext. 109</div></div><div>English, American Sign Language</div></div></div>