Bug 24387 - Rename News tool
Summary: Rename News tool
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement with 5 votes (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords: rel_21_11_candidate
: 25001 (view as bug list)
Depends on: 22544
Blocks:
  Show dependency treegraph
 
Reported: 2020-01-09 16:17 UTC by Caroline Cyr La Rose
Modified: 2021-05-03 09:43 UTC (History)
9 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Caroline Cyr La Rose 2020-01-09 16:17:31 UTC
Now that the 'News' tool serves a larger purpose than just adding news, we should rename it.

I suggest 'Content' or 'Custom content'. But it's just a suggestion. Feel free to change it to something else.
Comment 1 Owen Leonard 2020-01-09 16:37:00 UTC
Maybe "News and content" ?

It's technically redundant but I worry that people will wonder where News went.
Comment 2 Katrin Fischer 2020-04-05 14:54:30 UTC
*** Bug 25001 has been marked as a duplicate of this bug. ***
Comment 3 David Cook 2020-04-06 01:18:21 UTC
As I mention on https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25001, it seems the CMS functionality will use a heading of "Pages" with a description of "Create and edit additional content pages".

I've asked one librarian and they suggested "Interface customization" or "Home page customization" or something like that. 

Martin suggested "Blocks" or "Content blocks", which I quite like, since it implies that it's chunks of content rather than whole pages (like the CMS), but I don't think librarians will understand. 

Maybe "HTML customization"? But that would only work for tech savvy librarians. Maybe "Web page customization" or "Page customization", but then I worry about the overlap with the CMS functionality. 

That said, maybe we should frame it all with a "Edit content" or "Content" heading and then have subheadings for "Pages" and "Sections"?
Comment 4 Lisette Scheer 2020-04-09 15:20:20 UTC
(In reply to Owen Leonard from comment #1)
> Maybe "News and content" ?
> 
> It's technically redundant but I worry that people will wonder where News
> went.

+1 We still use this for news and I think it would confuse some of our folks who use that feature.
Comment 5 Lucas Gass 2020-04-09 16:13:57 UTC
Some librarians use a lot of News items (both in slips and in the the OPAC ). That makes for a lot of clutter once we start adding the HTML preferences. What are the thoughts of separating these into separate 'Tools'?

-News
-Another section for "HTML customization" or whatever is decided to call it
Comment 6 Lisette Scheer 2020-04-09 16:26:08 UTC
(In reply to Lucas Gass from comment #5)
> Some librarians use a lot of News items (both in slips and in the the OPAC
> ). That makes for a lot of clutter once we start adding the HTML
> preferences. What are the thoughts of separating these into separate 'Tools'?
> 
> -News
> -Another section for "HTML customization" or whatever is decided to call it

This is even better. Especially in consortium where different libraries might all be using the news for different things, it could be very clunky to have all the news + these content fields we are moving into the news.
Comment 7 Ed Veal 2020-12-13 17:05:19 UTC
I support separating news and html customizations.
Comment 8 Séverine Queune 2021-04-06 15:24:31 UTC
(In reply to Lucas Gass from comment #5)
> Some librarians use a lot of News items (both in slips and in the the OPAC
> ). That makes for a lot of clutter once we start adding the HTML
> preferences. What are the thoughts of separating these into separate 'Tools'?
> 
> -News
> -Another section for "HTML customization" or whatever is decided to call it


+1 to separate them !
Comment 9 Michael Adamyk 2021-04-07 21:28:46 UTC
+1 to separating them. News is extremely cluttered now (as a consortium).
Comment 10 Jonathan Druart 2021-04-08 09:49:31 UTC
Please help bug 22544 if you want to see this move forward.