Phase One "bare bones" functionality

[laryn]

Can we do an initial bare-bones phase where we get the skeleton (Backdrop/CiviCRM) in place and configured enough to allow people to create accounts, submit data, do a basic search/filter on a Views table that pulls from CiviCRM, etc. before the full roll-out of visual map, searchability, etc.? That way we'd be able to get people populating the data in a pre-official-launch phase.

• create accounts
• submit data
  • currently submitting data means making an instance of the business content type.
  • @todo: we need an API connection when a user submits a business we need to populate a CiviCRM New Business
    • We also need to think about syncing; what if a user updates a business on the Cive side what happens to the Backdrop business content or rather how to update it.
• do a basic search/filter on a Views table that pulls from CiviCRM
  • This is on the /businesses page (it is custom not a view, feeding in from the business content type)

[laryn]

@serundeputy What needs to happen to get this bare bones phase functional? Then they can start populating the site even if development is not complete yet. Some open questions:

• Syncing (as mentioned above): How do the CiviCRM entries and Backdrop business nodes get synced? (Some custom code in the submit handler on the Backdrop side? And then what about when a contact is edited or duplicates merged from the CiviCRM side?) Idea for discussion: CiviCRM Entity module port? (RE: CiviCRM contact <--> Backdrop Entity sync) #20
• Searching: Before allowing the creation of a new business, can we force them to search to see if it already exists?
• Submitting: After creating an account they should be able to submit a business. (And categorize it)
• Edits/ownership: How do we manage ownership? If they've created an account and submit/claim a business, they own it and should be able to edit it. But they should also be able to submit a business without claiming it. (More)
• Access while developing: Other features like the full design and map functionality can be phased in later (once we have content and time to develop it). But is there a way to open up the bare bones functionality to the public while also keeping the non-public parts hidden? (e.g. maybe using Shield to only open up certain URLs to the public and require a popup username/password for any other pages?)

[laryn]

@serundeputy @rick02840 and others, I have a new thought here. The entity syncing seems to be a major hold up so I'm wondering if we push all of that to Phase Two and for this alpha 'data collection' functionality we just use CiviCRM functionality (along with Webform CiviCRM). We allow people to do a basic search, add a new contact (linked to their contact info via CiviCRM relationship, indicate whether they want to "own/claim" this entry when that functionality is in place).

Any feedback before I try to mock this up on staging?

[rick02840]

Hi @laryn there was a Hack for Western Mass meeting on Tuesday so that's why I did a bit of work on this (updated Backdrop).
I think I need to understand his project better. I see an overview here: #6

...a directory of black-owned businesses in Memphis. This should end up being a kind of Yelp-lite, where the community can add, edit, and rate businesses. It seems like a Backdrop/CiviCRM solution could be appropriate

What confuses me a bit is why Civi is needed. What is described in the above can be done without Civi. Civi is great but it adds a LOT of complication that may or may not be needed for this site.

Looking at the original Jan 26 post above:

• create accounts
  I understand this
• submit data ( making an instance of the business content type)
  I understand this
• API connection when a user submits a business we need to populate a CiviCRM New Business
  I understand the idea, not not sure how to do it (but can look into it)
• syncing businesses
  ditto, understand idea, not sure how do it
• do a basic search/filter
  I understand this

Where is the staging site online located, and can we get login user / pass (not here obviously)?

And to answer your question: "The entity syncing seems to be a major hold up so I'm wondering ..."
Yes, that sounds like something that will not be simple. But hard to really answer anything without understanding the whole project: How Civi wants to be used, how the Drupal site wants to be used, etc.
Thanks!
Rick

[rick02840]

Also.... we'll need a way to easily grab a database backup from the staging site, since I assume that will be the "canonical" database where content it entered. Possibly getting a user/pass to that will allow export via backup/migrate, not sure... Or some other way.

[laryn]

@rick02840 I initially suggested the CiviCRM component because in inviting public input into the directory, it's inevitable that there will be duplicates created and I thought being able to use CiviCRM's deduplication process would be helpful. As well, the concept (especially in early phases) invites people to submit black owned businesses that they may not own (ie. without "claiming" them and keeping editorial control) and using CiviCRM would allow them to be attached to the business via a relationship, but not necessarily added as the author/owner of the business node.

This and because there is potential that BLM Memphis will use other CiviCRM features such as donations, CiviMail, etc. as part of the directory management (e.g. send a message to all businesses in a certain sub-category, etc.). And although I haven't even mentioned to them, as finances are tight everywhere and especially volunteer run orgs that subsist on personal donations, I was thinking that a long term possibility could be allowing a "membership" system (again via CiviCRM) so member businesses get highlighted in the listings in some way. I'm not sure if that is something they'd be interested in or not.

That said, in the early phase especially, I think a case could be made to do this the other way around and do a straight Backdrop setup and potentially import/link to CiviCRM in the future after there is more content and they are ready to scale up or adjust we could export/import/link the two sides. And using Backdrop features in this first phase may make sense as this is a #Backdrop4Good project, not a #CiviCRM4Good project. 😉

@serundeputy Any thoughts from your side? Also on the database backup question and how you think we should handle staging details/credentials in general.