Hi Espo folk,
Thank you kindly for taking the time to read my message and thank you in advance for any guidance.
I have Espo installed in a Docker container on my ubuntu VPS. I am a newbie. I have ADHD. I am attempting to build my own music business portal. It has been incredibly hard for me to get here, but here I am and I am excited! Espo is great.
I want to create a music catalogue module giving me and any users the ability to create 'Artist' records and then 'Recordings' and indeed 'Releases' There is of course shared metadata between them all - 'Artist Name' for example features in all. So three related entities. Ever expandable the simple overview is....
Artist: Artist Name, Biography, number of band members, a line for each band member holding their number, email and publisher, links to key social media.
Audio Asset: Recording Name, version, length, number of songwriters, a line for each songwriter with their name, publisher and %, Artist name(s).
Release: Release type, Release name, artwork,.Artist name(s), release date, catalogue number, barcode, p year and credit c year and credit. +++The ability to attach recordings.
In order to get to grips with this as efficiently as possible, it looks to me like the most efficient way of creating my entities might be via a custom module. I created a simple test module to attempt to install but I'm struggling to make this happen.
Could anyone please help me understand how best to create this? I am struggling. My brain is really not processing the entity manager in a useful manner so if creating it that way is the best way I would sincerely appreciate some plain English child instructions!
thank you so much for the time
I have a really exciting music business to hand which I am using espo for and if anyone wanted to trade espo help for music release strategy, guidance and the like... love to help, my resume is strong. Ha..just not for this!!
docker exec -it espocrm /bin/bash
cd /var/www/html/custom/Espo/Custom/Modules
mkdir MusicCatalogue
cd MusicCatalogue
touch metadata.json
echo '{
"name": "MusicCatalogue",
"label": "Music Catalogue",
"package": "custom",
"module": true,
"acl": true,
"metadata": {
"entityDefs": {
"Artist": {
"fields": {
"name": {
"type": "string",
"required": true,
"label": "Artist Name"
}
},
"labels": {
"singular": "Artist",
"plural": "Artists"
}
},
"Song": {
"fields": {
"name": {
"type": "string",
"required": true,
"label": "Song Name"
},
"artist": {
"type": "ref",
"refersTo": "Artist",
"label": "Artist"
}
},
"labels": {
"singular": "Song",
"plural": "Songs"
}
},
"Product": {
"fields": {
"name": {
"type": "string",
"required": true,
"label": "Product Name"
},
"song": {
"type": "ref",
"refersTo": "Song",
"label": "Song"
}
},
"labels": {
"singular": "Product",
"plural": "Products"
}
}
}
}
}' > metadata.json
cd /var/www/html
php clear_cache.php
Thank you kindly for taking the time to read my message and thank you in advance for any guidance.
I have Espo installed in a Docker container on my ubuntu VPS. I am a newbie. I have ADHD. I am attempting to build my own music business portal. It has been incredibly hard for me to get here, but here I am and I am excited! Espo is great.
I want to create a music catalogue module giving me and any users the ability to create 'Artist' records and then 'Recordings' and indeed 'Releases' There is of course shared metadata between them all - 'Artist Name' for example features in all. So three related entities. Ever expandable the simple overview is....
Artist: Artist Name, Biography, number of band members, a line for each band member holding their number, email and publisher, links to key social media.
Audio Asset: Recording Name, version, length, number of songwriters, a line for each songwriter with their name, publisher and %, Artist name(s).
Release: Release type, Release name, artwork,.Artist name(s), release date, catalogue number, barcode, p year and credit c year and credit. +++The ability to attach recordings.
In order to get to grips with this as efficiently as possible, it looks to me like the most efficient way of creating my entities might be via a custom module. I created a simple test module to attempt to install but I'm struggling to make this happen.
Could anyone please help me understand how best to create this? I am struggling. My brain is really not processing the entity manager in a useful manner so if creating it that way is the best way I would sincerely appreciate some plain English child instructions!
thank you so much for the time
I have a really exciting music business to hand which I am using espo for and if anyone wanted to trade espo help for music release strategy, guidance and the like... love to help, my resume is strong. Ha..just not for this!!
docker exec -it espocrm /bin/bash
cd /var/www/html/custom/Espo/Custom/Modules
mkdir MusicCatalogue
cd MusicCatalogue
touch metadata.json
echo '{
"name": "MusicCatalogue",
"label": "Music Catalogue",
"package": "custom",
"module": true,
"acl": true,
"metadata": {
"entityDefs": {
"Artist": {
"fields": {
"name": {
"type": "string",
"required": true,
"label": "Artist Name"
}
},
"labels": {
"singular": "Artist",
"plural": "Artists"
}
},
"Song": {
"fields": {
"name": {
"type": "string",
"required": true,
"label": "Song Name"
},
"artist": {
"type": "ref",
"refersTo": "Artist",
"label": "Artist"
}
},
"labels": {
"singular": "Song",
"plural": "Songs"
}
},
"Product": {
"fields": {
"name": {
"type": "string",
"required": true,
"label": "Product Name"
},
"song": {
"type": "ref",
"refersTo": "Song",
"label": "Song"
}
},
"labels": {
"singular": "Product",
"plural": "Products"
}
}
}
}
}' > metadata.json
cd /var/www/html
php clear_cache.php
Comment