Difference between revisions of "CKAN Administration"

Jump to navigation Jump to search
434 bytes added ,  14:06, 1 March 2022
Add bit about using CKAN metadata for centralizing operational ETL data
(Add bit about using CKAN metadata for centralizing operational ETL data)
Line 31: Line 31:
To add or change the departments belonging to a particular publisher organization edit the <code>dataset_schema.json</code> file: <code>> vi /usr/lib/ckan/default/src/ckanext-scheming/ckanext/scheming/dataset_schema.json</code>
To add or change the departments belonging to a particular publisher organization edit the <code>dataset_schema.json</code> file: <code>> vi /usr/lib/ckan/default/src/ckanext-scheming/ckanext/scheming/dataset_schema.json</code>


Then run <code>>sudo service apache2 reload</code>
Then run <code>> sudo service apache2 reload</code>


The extra tricky part about this one is that [https://github.com/WPRDC/ckanext-wprdctheme our GitHub repository that includes this JSON file] is installed in a different directory: <code>/usr/lib/ckan/default/src/ckanext-wprdctheme/</code> but changes to the files in that directory (and subdirectories) do nothing.
The extra tricky part about this one is that [https://github.com/WPRDC/ckanext-wprdctheme our GitHub repository that includes this JSON file] is installed in a different directory: <code>/usr/lib/ckan/default/src/ckanext-wprdctheme/</code> but changes to the files in that directory (and subdirectories) do nothing.


== Other changes ==
== Other changes ==
=== Using CKAN metadata instead of local caches ===
To avoid keeping local databases about datasets (for instance, when writing code to track some aspect of datasets), store such information (such as the last time an ETL job was run on a given package) in the 'extras' metadata field of the CKAN package, as much as possible. This stores information in a centralized location so ETL jobs can be run from multiple computers without any other coordination. The extras metadata fields are cataloged on the [[CKAN Metadata]] page.
=== Hacky workaround for adding new users to publishers ===
=== Hacky workaround for adding new users to publishers ===
In additional to adding the users to the organizations through the CKAN front-end, you also have to add them to groups, using this URL: [http://wprdc.org/group-adder/]
In additional to adding the users to the organizations through the CKAN front-end, you also have to add them to groups, using this URL: [http://wprdc.org/group-adder/]
== Other CKAN stuff ==
See the CKAN section of [https://github.com/WPRDC/knowhow-and-tricks].


[[Category:Onboarding]]
[[Category:Onboarding]]

Navigation menu