ckanext-dgu | CKAN extension for data.gov.uk

by datagovuk Python Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | ckanext-dgu Summary

ckanext-dgu is a Python library. ckanext-dgu has no bugs, it has no vulnerabilities, it has build file available and it has low support. You can download it from GitHub.

CKAN extension for data.gov.uk

Support

Quality

Security

License

Reuse

Support

ckanext-dgu has a low active ecosystem.

It has 29 star(s) with 35 fork(s). There are 8 watchers for this library.

It had no major release in the last 6 months.

There are 72 open issues and 239 have been closed. On average issues are closed in 34 days. There are 10 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of ckanext-dgu is current.

Quality

ckanext-dgu has 0 bugs and 0 code smells.

Security

ckanext-dgu has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

ckanext-dgu code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

ckanext-dgu does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

ckanext-dgu releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

ckanext-dgu saves you 20199 person hours of effort in developing the same functionality from scratch.

It has 39778 lines of code, 1638 functions and 341 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed ckanext-dgu and discovered the below as its top functions. This is intended to give you an instant insight into ckanext-dgu implemented functionality, and help decide if they suit your requirements.

Initialize the database
Fetches the list of authorities from the WDTK
Tries to guess the publisher publisher
Close the dataset and resource file
Run the report
Run the report
Return a list of all datasets in a given bounding box
Update the publisher info table
Generate the Openness scores for each publisher
Return the openness score for a given publisher
Generator for all sub - organizations of the organization
Execute the scraper
Return all resources with a scraper url
Execute the command
Return a dict of format dicts
Returns the formatted representation of the process
Returns a dictionary of format dictionaries
Show a user
Find the admins of a group
Try to suggest tags for a given package
Count the number of resources in a given publisher
Execute ckan command
Remember the identity of the user
Add an external publisher
Dump all installed packages
Add a value

Get all kandi verified functions for this library.

ckanext-dgu Key Features

No Key Features are available at this moment for ckanext-dgu.

ckanext-dgu Examples and Code Snippets

No Code Snippets are available at this moment for ckanext-dgu.

Community Discussions

Trending Discussions on ckanext-dgu

Changing publisher name and URL

Sync user's email between Drupal and CKAN

QUESTION

Changing publisher name and URL

Asked 2017-Apr-05 at 09:51

So, yeah, the form is saying:

Please contact the system administrator to change your publisher name

and I'm the system administrator for the project and I don't know what the hell am I doing. :)

I can change the name of the publisher but not the URL. I guess this also changes some URL in the dataset? Do I need to do the change with API or there is some GUI?

BTW. I'm using DGU package.

...

ANSWER

Answered 2017-Apr-05 at 09:51

You should ssh to your server and run commands like this to change the name, and optionally the title too with the -t:

Source https://stackoverflow.com/questions/43225964

QUESTION

Sync user's email between Drupal and CKAN

Asked 2017-Mar-17 at 16:54

I'm using dgu-vagrant-puppet and inside the system, when I log in and changed my email, things aren't in sync and probably I need to execute something to sync Drupal and CKAN.

Inside my file

...

ANSWER

Answered 2017-Mar-17 at 16:54

Yeah there is a bit of lag between the email being changed in Drupal and it being synced to CKAN. It is done when the user clicks on a CKAN page and the Drupal cookie/session is refreshed. This cookie refresh is after a login or when Drupal has refreshed the user session cookie, which if memory serves right is every 30 minutes.

The code that writes the change to CKAN is here:

https://github.com/datagovuk/ckanext-dgu/blob/45f41f1c58a6f60258c9d4d18a3ddcbd82d5f557/ckanext/dgu/authentication/drupal_auth.py#L222-L224

If you wanted, you could write a script to sync all users in one go, based on that code, calling DrupalClient to get the user details and writing them to the CKAN user.

Source https://stackoverflow.com/questions/42856481

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install ckanext-dgu

virtualenv pyenv pip -E pyenv install -e git+https://github.com:okfn/ckanext-dgu.git#egg=ckanext-dgu pip -E pyenv install -e git+https://github.com/okfn/ckan.git#egg=ckan pip -E pyenv install -r pyenv/src/ckan/pip-requirements.txt pip -E pyenv install -r pyenv/src/ckanext-dgu/pip-requirements.txt. There are plenty of other little details about getting CKAN running under Apache, SOLR config etc in the CKAN README.

Support

#Address and Connection errors. The missing settings that result in this error are to be found in {pyenv}/src/ckanext-dgu/test-core.ini which is also imported into {pyenv}/src/ckanext-dgu/test.ini, so make sure you are specifying either of these config files in your nosetests --with-pylons parameter. This is due to SOLR using the CKAN SOLR schema, rather than the specific DGU one. Change it using the ln -s command above, followed by stopping and starting SOLR.

Find more information at: