Importing Issue Metadata in CSV/DAT Load Files

OVERVIEW

Issue information can be imported for documents when loading with a
DAT/CSV load file.  However, doing so requires that the issue is set up
in Nextpoint first.  Then the load file should contain a column named
after the issue (or its prefix), with values specifying whether or not
the document is relevant to that issue.

Nextpoint  SETUP

In Nextpoint , use the "Settings" link to access the Label and Issue
configuration page.  Create each issue using the "New Issue" link,
paying careful attention to the name and prefix used to identify that
issue.  Also ensure that "Documents" is selected in the "Label applies
to:" section, or the issue won't be available for document importing.

Note: multiple issues can be named identically, but doing so makes
importing more difficult.  Also, for correct importing, issue
names/prefixes should not contain an equals-sign (=) and should not be
named "test".


LOAD FILE SETUP

In the load file, create a column for each issue that documents may be
imported for.  The column name should exactly match either the issue
name or issue prefix.

For each data row, the issue column(s) should contain a yes/no type
value, specifying if the document should be marked as part of the
respective issue.  The values "yes", "y", "true", "t", "x", and "*" (not
case sensitive) will be treated as "yes", and any other value will be
treated as "no".


FIELD MAP SETUP

When working with pre-existing load files that contain incorrect issue
column headings, it may be necessary to manually map the issues to
column names.  This is done with the fields.map (or fieldmap.txt) file,
where each line may contain a mapping as follows:

 issue_ISSUENAME = COLUMNAME

That is, the text "issue_", followed by the issue name (or prefix), then
an equals-sign, and the name of the column from the load file.  The
issue name and column name may contain spaces, like so:

 issue_My Issue = Issue Column

It is especially important to ensure that the column name is written
exactly like the column heading (case sensitive), however the "issue_"
and issue name/prefix are not case sensitive.


EXAMPLES

For the following examples, we will have two issues, created in
Nextpoint  as:

 Name:   Research
 Prefix: R

 Name:   Development
 Prefix: Dev

An example load file might look like:

 SHORTCUT, IMAGE_FILE, RESEARCH, DEV
 study 1, study_1.pdf, yes, no
 project 1, project_1.pdf, -, X
 study 2, study_2.pdf, y, n

In another case, when a map file is needed, you may have:

 Load file:

 SHORTCUT, IMAGE_FILE, ISS_Rsrch, ISS_Devel
 study 1, study_1.pdf, yes, no
 project 1, project_1.pdf, -, X
 study 2, study_2.pdf, y, n

 Map file:

 issue_r = ISS_Rsrch
 issue_development = ISS_Devel