Drupal 7 Module, for Team Roster content type, classic one-to-many database relationship
$100-120 USD
Σε Εξέλιξη
Αναρτήθηκε περίπου 12 χρόνια πριν
$100-120 USD
Πληρωμή κατά την παράδοση
I need to implement a content type (or entity) in Drupal 7 to represent a sports team roster. It will need to be in the form of a classic relational database one-to-many relationship, with a number of fields on the "one" side, and zero or more team players on the "many" side.
Please see detailed requirement for specific project needs.
## Deliverables
I need to implement a content type (or entity) in Drupal 7 to represent a sports team roster. It will need to be in the form of a classic relational database one-to-many relationship, with a number of fields on the "one" side, and zero or more team players on the "many" side.
I really want the user to be able to enter all this information in a single form, with the "one" fields at the top of the form, then a table representation (or something that resembles a table) to enter the player information.
A user might create a team roster entering only the information at the top, leaving the team players blank, then come back at a later time to fill out the players. The team roster might be edited multiple times until the date of the actual event (the date an actual tournament begins).
I think this needs to be a custom module of some sort, as I have been unable to figure out how to do this with any available Drupal contributed modules. However, I am willing to pay for someone to show me how to do this with contributed modules if it can be done.
Ideally, I would like this new entity (if that's the right word) to be "fieldable", but it's not necessary as long as the code is readable enough that I can modify it to add fields. I am very well-versed in PHP; I just am not comfortable enough with Drupal module development to get this task done.
I also need it fast. I have a hard deadline of just a few days, and I will need to incorporate this into a larger project.
Here are the fields needed. Of course, if the entity is fieldable, I can add these when I create the content type.
On the "one" side of the relationship; the "Team Roster":
Team name (the title)
Age group (options: 18U, 17U, 16U, 15U, 14U)
Head Coach Name
Head Coach Phone
Head Coach Email
Asst Coach Name
Asst Coach Phone
Asst Coach Email
On the "many" side, for each team player:
Number (an integer)
Name
Position (Options: P, C, INF, OF, SS, 1B, 2B, 3B, Util)
Bat (Options: Left, Right, Switch)
Throw (Options: Left, Right)
Weight (integer)
Height (Range: 48..84, displayed as 4'0"..7'0" [feet' inches"])
High School
Grad Year (Range: current year-2 .. current year+10)
Email
Now, of course, if these are entirely fieldable, the module need not define these fields. However, if the fields need to be defined in the module code, that's fine too.
In your proposal, please tell me how you plan to implement this, whether it be an entity module, a field module, usage of Drupal 7 contributed modules, etc.
Thank you for considering this project.