adds project name field

[capetillo]

Adds optional "name your project" field in the frontend and the backend sends it back in the output. If you have suggestions for better wording, please suggest it

[jnation3406]

Why are we naming an operation? It already has a "source" name and its input file set, why do we need a human name too?

[capetillo]

Why are we naming an operation? It already has a "source" name and its input file set, why do we need a human name too?

we don't always use source name. human name is so that when users download the light curve, they know what that light curve belongs to. because it's not always the basename (e.g. ngc7331)

[jnation3406]

Why are we naming an operation? It already has a "source" name and its input file set, why do we need a human name too?

we don't always use source name. human name is so that when users download the light curve, they know what that light curve belongs to. because it's not always the basename (e.g. ngc7331)

I would say in that case we should just prompt them for a filename when they click to save the plot? Or call it something like "lightcurve_of_ra123123xdec123123" if they don't specify a source name. No need to add a name to the operation itself I think.

[capetillo]

Why are we naming an operation? It already has a "source" name and its input file set, why do we need a human name too?

we don't always use source name. human name is so that when users download the light curve, they know what that light curve belongs to. because it's not always the basename (e.g. ngc7331)

I would say in that case we should just prompt them for a filename when they click to save the plot? Or call it something like "lightcurve_of_ra123123xdec123123" if they don't specify a source name. No need to add a name to the operation itself I think.

@markBowman @sfoale what do you two think?