Auto-generated forms (CSV)

Epic
Document status	DRAFT

Goals

#	Title	User Story	Notes
1	Connecting the the CSV file	As a user I need to be able to set the network location of the CSV file. As a user I need to specify if the source of the file is normal or streaming.	Normal mode vs. streaming mode.
2	Limit processing	As a user I want to tell the system that only certain files at the network location should be processed.	eg. regex pathInclude, pathexclude
3	Mapping records	As a user I need a way to map my records onto the metadata object. In this way, I can verify that the data in my CSV file is properly represented in the source. As a user I want to manually specify the field names by plugging them (eg. array) or As a user I want the system to automatically detect header rows and field names with a minimum of configuration. Header Not Prefixed by a String: As a user, If the header row is not prefixed by a string then I will need a mechanism to help the platform "pull out" the header field. This could be an object-oriented configuration language or UI element of some kind for supporting non-standard SV files (eg. records spanning more than one line).	Auto: Header prefixed by strong vs. header not prefixed by string.
4	Special characters	As a user I need to be able to change the separator, quote and escape characters if my data does not match the default formatting.

Read the story map from top to bottom and left to right. Baseline elements are identified using Priority 1.

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome