Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Epic
Document statusDRAFT

Goals

Background and strategic fit

Assumptions

Requirements

#TitleUser StoryImportanceNotes
1Connecting 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.
2Limit processingAs a user I want to tell the system that only certain files at the network location should be processed. eg. regex pathInclude, pathexclude
3Mapping 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.

 

 

 

Auto:

Header prefixed by strong vs. header not prefixed by string.

4Special charactersAs a user I need to be able to change the separator, quote and escape characters if my data does not match the default formatting.  

User interaction and design

Questions

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

QuestionOutcome

Not Doing

  • No labels