CSV Import file

preparing import metadata (csv file) as a purple user you can upload a csv file containing metadata and file references for the issues you wish to import the purple importer constantly checks (every few minutes) to see if a new csv file has been uploaded or if existing ones have been updated a csv file can be placed anywhere in the directory and the importer will find it the csv (comma separated values) file is a simple and widely used file format for storing tabular data, such as spreadsheet or database information csv requirements for purple in a nutshell csv requirements for purple in a nutshell use only semicolon (;) as a delimiter do not use any other delimiter each row of the csv file must specify exactly one issue use only utf 8 as text encoding when saving the csv files do not use additional delimiters such as comma, tab etc the csv file has to end with " csv " here's a more detailed breakdown of the general setup delimiter purple csv files use exclusively semicolon (;) as a delimiter to separate the values in each row it is very important not to use any other available delimiter as this would result in the file getting broken rows and columns like a table, a csv file consists of rows and columns each row represents a separate entry or record, and each column represents a specific attribute or piece of information related to that entry column headers typically, the first row of a csv file contains headers, which are names or labels for each column these headers describe the data in each column and help users understand what each column represents the sample graphic below shows the first row containing the column headers (dark blue) following the header row which contains the column headers, each subsequent row contains the actual data values these values are separated by the delimiter and correspond to the columns defined by the headers mandatory mandatory header types header types column header description folder relative path to your input file publication publication name in purple manager issue name the issue name displayed in app/web experience publication date date/time that will be set as publication date for the issue recommended header types recommended header types true false 183false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type additional header types true false 183false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type additional information to colum headers the issue name is used as the unique identifier for the publication and therefore has to be unique within a publication referencing the same file from multiple csv lines a file can be referenced from more than one line in the csv file however, the purple importer requires a unique one to one relationship between a csv line and a file reference in order to support multiple references to the same file, the importer does some preparation work while collecting the output data from sftp the importer breaks the many to one relationship between the csv lines and each file reference by creating a unique copy of the file for each individual csv line this is done by appending a unique (within the scope of the csv file), repeatable string to the file name when this is done, the original file is deleted this is necessary for the importer to work properly these copies are visible on the sftp and should not be touched publication date the following date formats are allowed yyyy mm dd hh\ mm\ ss yyyy mm dd dd m yyyy hh\ mm\ ss dd m yyyy dd/mm/yyyy hh\ mm\ ss dd/mm/yyyy year abbreviation by two digits (f e “ 18 ” for “ 2018 ”) is also supported for every date format issue access the issue access can be specified per issue in the csv, or globally in the users config yml file (only very limited persons have access to that file) possible values free (content is available for everyone and visible in the app/web experience paid (content is visible but locked and usually unlocked by purchasing it) locked (content is avilable to entitled users and invisible until unlocked) if no explicit value for "access" is given the default mechanism is used to determine if an issue is paid or free content the default mechanism sets the issue as paid content when any product id (ios, android) is set sample file https //archbee doc uploads s3 amazonaws com/ygr6ktt9qi r0u3uktjsm/tcxnevzmgdka0fdalxw2k import csv