artefactual / archivematica-devtools Goto Github PK

Much of the work done in this repo is based on interfaces that are not public APIs, e.g. graph-links accesses to the database and expect connection parameters to be located at a certain location - in this case the simplest compromise is to convert it into a django-admin command of the main app in the dashboard because that's where the models live and the dashboard knows how to access to the database. Each devtool has its own story so they'll have to be revisited individually.

Note: get_fpr_changes and import_pronom_ids were already implemented in archivematica-fpr-admin: see https://github.com/artefactual/archivematica-fpr-admin/tree/stable/1.6.x/fpr/management/commands.

Currently following @timothyryanwalsh's instructions in METSFlask to explore the tool a little more.

https://github.com/timothyryanwalsh/METSFlask#detailed-identification-and-dates

I get the following:

 vagrant@vagrant:~/git/artefactual/archivematica-devtools$ sudo am ensure-fits-characterization
 Traceback (most recent call last):
   File "/usr/local/libexec/archivematica/ensure-fits-characterization", line 34, in <module>
     import django
 ImportError: No module named django

AM 1.6.1.

If I start trying to add the dependencies, e.g. pip install django, then we seem to step into a rabbits den of other dependency issues. One odd one is 'Import, no module named webdesign' which seems to be coming from the initialisation of the django.contrib modues and should be there once django is (other contrib modules are).

Is my expectation wrong to be able to do this from the Vagrant installation of AM?

tools like restart-services and services (from #35 ) only work with upstart, and will fail on platforms that use systemd.

There may be other os specific issues in other tools, I haven't checked.

It should be the date the aip was ingested

The contributing.md needs to be updated to reflect how we want issues filed in the new repo, as well as an issue template encouraging the use of the new repo.

Traceback (most recent call last):
File "/opt/archivematica/libexec/archivematica/reindex-index-data", line 29, in
import elasticSearchFunctions
File "/usr/lib/archivematica/archivematicaCommon/elasticSearchFunctions.py", line 39, in
from main.models import File, Transfer
File "/usr/share/archivematica/dashboard/main/models.py", line 34, in
from django_extensions.db.fields import UUIDField
ImportError: cannot import name UUIDField

Occasionally on running vagrant up, the dashboard doesn't load. Restarting services using am services results in the following error:

* Restarting web server apache2 
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Action 'start' failed.

This was on a recent dev branch of Archivematica and qa/0.x of the SS, but it happens regularly with 1.6.x and stable/0.9x as well.

The README docs for the devtools could use some updating/clarifying. This is the only place where many of these tools are documented, so it would be great if it were more thorough. Alternately, the info could be added to the main documentation.

linktool currently produces SQL, but as of Archivematica 1.5 migrations are done using Django migrations instead of SQL migrations. linktool needs to be updated to produce Django migration output.

This is the traceback:

Traceback (most recent call last):
  File "rebuild-transfer-backlog", line 185, in 
    main()
  File "rebuild-transfer-backlog", line 173, in main
    process_transfer(es_client, os.path.join(transfer_backlog_dir, directory), sharedDirectory)
  File "rebuild-transfer-backlog", line 106, in process_transfer
    elasticSearchFunctions.connect_and_index_files('transfers', 'transferfile', uuid, path)  # AM 1.5
AttributeError: 'module' object has no attribute 'connect_and_index_files'

A new feature request from an Artefactual client - create a new tool to allow an AIP that was stored in one Archivematica Pipeline to be imported into another Archivmeatica environment. The main use case is when a set of AIP's were produced and saved with an Archivematica instance that no longer exists.

The tool should allow a user to provide the path to a locally available AIP and the tool will:

• validate the AIP (make sure it is a valid Bag
• add an entry to the storage service database
• index the aip in the local ElasticSearch index