Python Implementation of NACO Normalization Rules
The Name App is a tool originally developed for documenting names used by the UNT Libraries in its various digital library systems and collections. The app provides a consistent way of communicating the authorized version of a name and information about the name that is useful for reuse. The Name App generates a unique URL for each name that can be used to unambiguously refer to a person, organization, event, building or piece of software. In addition to an HTML page for each name there are a number of other formats available for each record including a MADS XML version and a simple JSON representation. A key feature of the UNT Name App is the ability to link to other vocabularies such as the Virtual International Authority File (VIAF), the Library of Congress Name Authority File, or Wikipedia.
For installation instructions, see the Installation page in the docs.
See LICENSE.
django-name was developed at the UNT Libraries.
Contributors:
- Joey Liechty
- Damon Kelley
- Lauren Ko
- Mark Phillips
- Gio Gottardi
- Madhulika Bayyavarapu
- Gracie Flores-Hays
- Trey Clark
- Python 3.9 or later
There are three ways to set up this environment locally.
Install Docker. Instructions differ based on installation method.
Clone the repository.
$ git clone https://github.com/unt-libraries/django-name.git
$ cd django-nameWarm up the Mariadb database. This only needs to be done when the database container doesn't exist yet. This will take about a minute once the image has been pulled.
$ docker compose up -d mariadbStart the app and run the migrations.
# start the app
$ docker compose up -d
# run the migrations
$ docker compose run --rm web ./manage.py migrate
# optional: add a superuser in order to login to the admin interface
$ docker compose run --rm web ./manage.py createsuperuserAt this point you should be able to access your local instance of the site by visiting <dockerhost>:8000/name/
The code is in a volume that is shared between your workstation and the web container, which means any edits you make on your workstation will also be reflected in the Docker container. No need to rebuild the container to pick up changes in the code.
However, if the requirements files change, it is important that you rebuild the web container for those packages to be installed. This is something that could happen when switching between feature branches, or when pulling updates from the remote.
# stop the app
$ docker compose stop
# remove the web container
$ docker compose rm web
# rebuild the web container
$ docker compose build web
# start the app
$ docker compose up -d$ sudo dnf install podman-composeYou will follow the same steps as above, starting with Clone the repository. For all of the docker steps, you will have to replace the word docker with podman.
If you have SELinux, you may need to temporarily add :Z to the web volumes in the docker-compose.yml. It will look like .:/app/:Z. You may also need to use sudo for your podman-compose commands.
Clone the repository.
$ git clone https://github.com/unt-libraries/django-name.git
$ cd django-nameInstall the mysql development package. The command depends on your system:
# Red Hat
sudo dnf install mysql-devel
# Ubuntu / Windows (WSL)
sudo apt install libmysqlclient-dev
# macOS via Homebrew
brew install mysql-clientCreate a virtual environment and activate it
$ python -m venv env
$ source env/bin/activateInstall the dev dependencies
$ pip install .'[dev,test,codestyle]'Replace the DATABASES Django setting in ./tests/settings/dev.py with
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': './db.sqlite3',
}
}Add table data
$ python manage.py migrateStart dev instance
$ python manage.py runserverThe app should be available at http://localhost:8000/name/
NOTE: tests will not pass without the mariadb and postgres databases available.
To run the tests via Tox, use this command. If you are using podman-compose, swap the word docker with podman for the commands below.
$ docker compose run --rm web tox