Decide repository structure for managing requests

[agstephens]

Initial idea:

requests/
  core_current/
  core_historical/
  user_current/
  user_historical/

[agstephens]

File-naming

File names for user requests

User requests:

user_id${numeric_user_id}_${submission_date}_hs${helpscout_ticket_number}_${request_number}.txt

Where:

• $submission_date is YYYYMMDD
• $request_number is 1 by default. If there are more then increment by 1 each time.

Example:

user_id23445_20211204_hs34582_1.txt

File names for core requests

Core requests:

core_${submission_date}_${informative_label}.txt

Where:

• $informative_label is a hyphen-separated string containing useful information

Example:

core_20190627_historical-all-models.txt

[agstephens]

Issues regarding directory structure

Logging history of completed user requests

Take this example:

requests/user_current/user_23445_20211204_34582_1.txt

When completed, we move it to:

requests/user_historical/${completion_date}/user_23445_20211204_34582_1.txt

Where $completion_date is the date we manually/automatically moved the selection file from the user_current location to the user_historical location.

[agstephens]

@alaniwi Please create the structure and put the current request into it.

[alaniwi]

Done.

[agstephens]

Keep open until we have documented all this.