💡 Create Javascript Input Form and EOS transaction package
User Story
As a user submitting data, I would like there to be a form to input my data and package it as an EOS transaction in order to provide easily parsable event source for the back-end.
Description
Form should have:
Source link
Release Name
Release Date
Label
Tracks
Group Name
Personnel
[member or guest]
Liner notes
The blockchain transaction should package these answers either into JSON that can then be later translated, or directly as graph database commands to build the graph database.
Source link: (with one field "link")
Release Name: (with one field "name" and a + button to add more)
Release Date: (with one date selector (year required))
Label: (with two fields [name, location]
Tracks: (with fields [link; name; duration; songwriter; cover? toggle y/n with greyed out field "original songwriter" unless y]; "edit details" button that allows users to edit the group name and personnel for each track, button is greyed out unless... )
["same details for all tracks" toggle underneath the tracks is by default on, allows "edit details" button to be pressed if turned off.]
Group Name: (with one field and a + button to add more groups)
Personnel: (with two fields [name and role] and one toggle with two options [member or guest] and a + button to add more people)
Liner notes: (with a big field)
The blockchain transaction should package these answers either into JSON that can then be later translated, or directly as graph database commands to build the graph database.
chillsauce
commented
1 year ago
💡 Create Javascript Input Form and EOS transaction package
User Story
As a user submitting data, I would like there to be a form to input my data and package it as an EOS transaction in order to provide easily parsable event source for the back-end.
Description
Form should have:
Source link Release Name Release Date Label Tracks Group Name Personnel [member or guest] Liner notes
The blockchain transaction should package these answers either into JSON that can then be later translated, or directly as graph database commands to build the graph database.
Solution
[add proposed solution, groomed feature description]
Source link: (with one field "link") Release Name: (with one field "name" and a + button to add more) Release Date: (with one date selector (year required)) Label: (with two fields [name, location] Tracks: (with fields [link; name; duration; songwriter; cover? toggle y/n with greyed out field "original songwriter" unless y]; "edit details" button that allows users to edit the group name and personnel for each track, button is greyed out unless... ) ["same details for all tracks" toggle underneath the tracks is by default on, allows "edit details" button to be pressed if turned off.] Group Name: (with one field and a + button to add more groups) Personnel: (with two fields [name and role] and one toggle with two options [member or guest] and a + button to add more people) Liner notes: (with a big field)
The blockchain transaction should package these answers either into JSON that can then be later translated, or directly as graph database commands to build the graph database.
👨💻 Deliverables
Design
Smart Contract
Backend
Frontend
Infrastructure
Testing
Marketing
Documentation