You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Historian has been making spreadsheets / tables of each event that happens during the semester and whether we have pictures for that event.
We have all the data to generate this automatically, so we can save Historian some time.
This feature requires #64 to be implemented, so that we can associate Photographers w/ Events.
There are a few possible ways to go about this:
The node-api generates a CSV file w/ Date of Event, Time of Event, Event Name, Committee Name, List of Photographers, (and if possible, the Week # each event took place). We'd either have to make a shell command to make this file or a button in the OneRepo to hit an endpoint and generate it. [Difficulty: Easy, Time: Medium]
We query the node-api for Events w/ Photographers from the OneRepo and make a printer-friendly page which displays this information in a table (so that you could print the page, or for example, in Chrome, "Print" -> "Save As PDF") [Difficulty: Easy, Time: Medium]
The node-api generates a PDF file directly of 2. [Difficulty: Hard, Time: Long]
@DanSwtmn How are you currently using this data? Which way helps you the most?
The text was updated successfully, but these errors were encountered:
Currently, Historian has been making spreadsheets / tables of each event that happens during the semester and whether we have pictures for that event.
We have all the data to generate this automatically, so we can save Historian some time.
This feature requires #64 to be implemented, so that we can associate Photographers w/ Events.
There are a few possible ways to go about this:
node-api
generates a CSV file w/ Date of Event, Time of Event, Event Name, Committee Name, List of Photographers, (and if possible, the Week # each event took place). We'd either have to make a shell command to make this file or a button in the OneRepo to hit an endpoint and generate it. [Difficulty: Easy, Time: Medium]node-api
for Events w/ Photographers from the OneRepo and make a printer-friendly page which displays this information in a table (so that you could print the page, or for example, in Chrome, "Print" -> "Save As PDF") [Difficulty: Easy, Time: Medium]node-api
generates a PDF file directly of 2. [Difficulty: Hard, Time: Long]@DanSwtmn How are you currently using this data? Which way helps you the most?
The text was updated successfully, but these errors were encountered: