• Resolved mmturner

    (@mmturner)


    Hi there,

    I just started with this great plugin so please forgive me if my question might be too simple.

    I’m trying to set up a record/music archive page. I set up pods for “artists”, “songs” and “records” so far. A record can have multiple songs and artists which works well.

    I would like to include “contributors” to the record for example musicians. The challenge is that the same musician might have played trumpet on one recording but trombone on the other. So that connection of musician and role/instrument is not static.

    What I like to achieve is that I have a custom field in “record” that is in relationship with “contributor” and connected to another one probably a text field where I could type in the role that musician has on the specific record.
    So I could generate for example a list like
    Musician 1: Trombone
    Musician 2: Trumpet

    I hope it’s understandable what I try to achieve. Any hints if and how this is possible would be highly appreciated.

    Thanks a lot in advance
    Merten

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Jory Hogeveen

    (@keraweb)

    Thread Starter mmturner

    (@mmturner)

    Hi Jory,

    thanks a lot for your answer. I understand the basic concept here but I still have problems to connect the second information/field.

    My parent pod is “Records”. The related pod “persons”.
    I set up the link table pod “contributions” (just like the other two pods?).
    This one has two fields: “contributor_person” which is related to “Persons”.
    The second one is a plain text field “contributor_role”.

    In my parent pod “records” I set up a field “record_contributor” which is related to “contributors”.

    The backend only shows me the drop down to chose the contributor(person) but not the text field “contributor_role” to put in the individual role.

    Thanks again and sorry if this is a stupid one… ??.

    Merten

    Plugin Author Jory Hogeveen

    (@keraweb)

    Hi @mmturner

    Good job so far!
    To answer your question, this is correct. Inline editing is at this point not possible (yet). We do have an open issue for this: https://github.com/pods-framework/pods/issues/5621

    For now you can use the edit icon in the relationship field. This will open the modal in which you can edit the link table relationship.

    As for the dropdown, this should show the relationship title. If this is indeed the person/contributor then that is correct but you could also use a combination of the link fields to create the contributor title like name - role. This way it’s easier to find the correct contributor link relation.

    Cheers, Jory

    Thread Starter mmturner

    (@mmturner)

    Thanks Jory,

    so that means that I would need to set up a post for each contribution combination. This I guess is not very practical. Inline editing wouldn’t help here as well because I would change the field globally.

    Contributions
    Musician 1: Flute
    Musician 1: Trombone
    Musician 1: Trumpet

    That also means that the permalink would lead to the contribution’s post page not to the person (musician) page. Is there a way to get a “nested” permalink?

    It would be great to be able to set up a field combinations where you can individually combine fields.

    But maybe I still haven’t understood the concept completely and make a mistake here.

    Thanks M.

    Plugin Author Jory Hogeveen

    (@keraweb)

    Hi @mmturner

    This I guess is not very practical. Inline editing wouldn’t help here as well because I would change the field globally.

    This would only be an issue if you re-use these relationships.

    That also means that the permalink would lead to the contribution’s post page not to the person (musician) page. Is there a way to get a “nested” permalink?

    The link table pod should be private, not public. The sub-relationship permalinks can be pulled using our traversal magic tags: {@contributor.person.permalink}.

    It would be great to be able to set up a field combinations where you can individually combine fields.

    I understand, but at this point Pods simply doesn’t support a group field with subfields. Also, in terms of DB structure this isn’t really preferable.

    Cheers, Jory

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Beginner’s question regarding concept’ is closed to new replies.