Closed practicalparticipation closed 9 years ago
It should definitely be easy enough to do it at the UI level, just by changing the content type. Not sure if i18n tools would be necessary or worth it? Unless using String overrides or similar.
Great - we should probably keep 'groups' as the underlying name for compatibility with CKAN APIs etc, but if it's just being picked up in most places from the content type then just changing display name might be enough.
Done some obvious name changes. Tried using Features Overrides which was ok for some bits but not others, so have just renamed some bits on live in db for now.
Looks good. Do we have quick docs of which bits have to be renamed in live in case changes reverted by future upgrades?
@stevieflow might have a view on whether we should do this or not - but if it is reasonably easy to use i8ln tools to over-ride the term 'groups' from DKAN with 'Organisations' this would make things more user friendly I think.