need to re-import [ +separation of application in client projects?]

[cccs-ip]

I was poking around the doc-meta front end on 'abadi'. I noticed that our logs folder was showing, so I re-set that to collect in a different S3 bucket and deleted the folder from the file system. I also merged together two 'project documentation' folders into one (now called project-documentation_ESMS), as the spreadsheet I supplied to you with meta-data also combines these two folders into a single group. I suspect we'll have to re-run the importer?

I look forward to seeing the abadi documents populated with metadata

I would normally raise this issue in our client project site. I raise it here b/c I am not seeing a 'doc meta' module in GitLabs for abadi. Please let me know if I am missing something.

[pwhipp]

Yes, this requires deletion and rebuilding of the docmeta document objects. Importing data into abadi should really be reported in the abadi issues. The docmeta github issues are for issues with the docmeta module itself.

docmeta is a completely separate project. There are no docmeta files in the Django space.

The importer is in docmeta. It picks up the project settings in order to get the right s3 bucket which is how it remains agnostic about the project it is in.

Python looks at the sys.path when finding a module (import sys in a shell to examine this). Normal python modules will be in the appropriate lib which will be on the path. This is also true of docmeta. setup.py will either add docmeta to the appropriate lib folder (setup.py install) or add its path to the sys.path (setup.py develop).

The reason 'Django' modules (they are really just python modules) appear under the project folder is because we routinely add this folder to the sys.path (that is the 'add2virtualenv .' instruction).

I'll rebuild the data when I've been through #1. Let me know if you need it done sooner.

[cccs-ip]

Thanks, Paul. As noted, I don't see an appropriate place yet in the client 'abadi' site (even though the module is there). Am I missing something?

[pwhipp]

Hopefully our discussion covered your comment. This issue can be closed. I'm raising the other issues shortly.