====== File Content Intelligence Administration ======
== last update on Aug 25, 2022 ==


===== Introduction =====

File Content Intelligence (FCI) is a feature designed for use by organisations that 		process electronic media assets.  

===== Audience =====

This document is written for Access Anywhere's Linux system administrator, its appliance administrator (appladmin) and its media tenant's organization administrator (org. admin.).  It explains how to set up Access Anywhere so file Content Intelligence can be used.  

===== Document Scope =====

File Content Intelligence supports two kinds of media file processing features: local processing and remote processing.  The local processing features depend on services that are bundled with Access Anywhere. Configuration of local processing features is covered in this document. The remote processing features depend on uploading assets to a cloud service provider for processing, then downloading the results. Configuration of remote processing services is not covered in this document.  Please contact [[mailto:support@nasuni.com|Support]] if you need help configuring the remote processing services.

This document does not cover how to use File Content Intelligence. [[https://www.youtube.com/watch?v=uBpFiv8Gm7M&feature=youtu.be|Here]] is a link to a video that shows how to use  File Content Intelligence.

See also:

[[/automationrules|Data Automation Rules]]

===== Setup Instructions =====


==== Linux System Administrator ====


SSH in to Access Anywhere as the user: smeconfiguser. Then use the smeversion command to confirm that v1906 or above of Access Anywhere is installed:

<code>
[smeconfiguser@b1b996ae ~]$ smeversion
1906.06
[smeconfiguser@b1b996ae ~]$ 
</code>
You must be running v1906 or later.  If you are not, please contact your organization's Access Anywhere appliance administrator to arrange an upgrade.

Confirm that the required containerised services are running by ssh’ing into Access Anywhere VM, becoming root and running this command: <code>
docker inspect --format='{{.Name}}' $(sudo docker ps -aq --no-trunc) | grep content-extraction
</code>
You should see output something like this: <code>
	/content-extraction_ce-api_1
	/content-extraction_ce-worker-go_1
	/content-extraction_redis_1
</code>
The three items that begin with “/content-extraction” must be listed in the output for CE to work as intended.  If they are not, please contact [[mailto:support@nasuni.com|Support]].

If you are using v1906.06 or earlier, still ssh’d in and now working as the smestorage user add this line to config.inc.php: <code>

	var $microservicesrestendpoint = 'http://127.0.0.1:2000/';
</code>
(Here is a link to instructions for editing that file: [[/appliance/editing-config]] )

==== Appliance Administrator ====

Working through the web interface as appladmin, on the Lickense Key page access from the Settinge menu confirm that your license key has the "Content > Extraction" and "Content > Deep Search" options enabled:
{{ ::license_key.png?direct&400 |}}

Still working as appladmin, make sure that Content Search / Solr Data Indexing is enabled on the Search Integration page accessed from the Settings menu:
{{ ::solr_indexing_on.png?direct&600 |}}
Still working as appladmin, use the User Packages option from the hamburger ment to access the list of packages, click on the pencil icon next to the package that is assigned to the org. (tenant) that will be using FCI, and on the Edit Packages page ensure that the "Content Search Enabled" and "Content Extraction" options are activated:
{{ ::content_search_enabled.png?direct&400 |}}

{{ :content_extraction_enabled.png?direct&400 |}}
This is a multi-select list. Be sure to use the appropriate key (Ctrl or CMD) when adding or removing selections so other selected items will remain selected.

Save your changes with the Save button at the bottom of the page.

==== Tenant Organization Administrator ====


Now working through the web interface as org. admin, select Content Intelligence from the Organisation menu and enable it on the Content Intelligence page:
{{ ::content_intelligence_enabled.png?direct&400 |}}
On the Services list, turn on “MD5 digest for a file” and “mediainfo tool results”.  Turn off the remainder of the items on the Services list, all of which begin with “Google”: 
{{ ::content_intelligence_services.png?direct&400 |}}

Expand the selection section under “media info tool results” to see or change the set of file types from which media info will be extracted:

{{ ::media_info_file_types.png?direct&400 |}}
Use the Update button to save your preferences, and the local services features of File Content Intelligence are ready for use.