Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the name of the default survey to "Untitled survey" #1647

Closed
brandonrosage opened this issue Mar 16, 2017 · 8 comments
Closed

Change the name of the default survey to "Untitled survey" #1647

brandonrosage opened this issue Mar 16, 2017 · 8 comments

Comments

@brandonrosage
Copy link

brandonrosage commented Mar 16, 2017

User story: I want to know what I can change about the data in my deployment. I want to be able to easily figure out what's editable and what's fixed.

To keep in step with our implementation of first-time deployers' on-boarding experience -- and to encourage the customization of surveys -- I'd propose we change the name of the out-of-the-box survey from "Basic post" to "Untitled survey."

"Basic post" is not useful or descriptive. Worse, though, is that it doesn't beg to be changed, or imply that it can be. "Untitled survey" accomplishes the following:

  • It describes what it is: A survey; not a post
  • It implies that it needs to be titled.
  • It uses the same convention for suggesting an edit -- "Untitled" -- as Google Drive files (e.g. Docs, Sheets, Forms) do for their document titles & names.

Aha! Link: https://ushahiditeam.aha.io/features/PROD-623

@jshorland jshorland added this to the UX clean up milestone Feb 26, 2018
@rowasc rowasc removed this from the UX clean up milestone Sep 13, 2018
@rowasc rowasc added this to the Parking Lot milestone Sep 4, 2020
@muchirijane
Copy link
Contributor

Hey @Angamanga , Could I please work on this issue for the outreachy contribution.

@Angamanga
Copy link
Contributor

@muchirijane This needs triage so it is not open for the community yet. Please check out this link if you can find something else you are interested in: https://github.com/ushahidi/platform/issues?q=is%3Aopen+is%3Aissue+label%3A%22Community+Task%22 We are adding more issues continuously but due to the large interest in Outreachy this year we are lagging behind. Please bear with us :)

@muchirijane
Copy link
Contributor

Noted. Thank you.

@rowasc rowasc added the Community Task Issues that the Ushahidi OSS community is encouraged to contribute to label Oct 9, 2020
@rowasc
Copy link
Contributor

rowasc commented Oct 9, 2020

I'm officially entering this one into "Community task" status @muchirijane assigning it to you so you can work on it. Keep in mind this will involve not just the change in the code, but a change in user docs as well which @CeciliaHinga may need to guide you through

@muchirijane
Copy link
Contributor

muchirijane commented Oct 9, 2020

Hey @rowasc, Thank you. I will work on it. Yes, I would absolutely appreciate some guidance.
Is the code to this specific issue in the platform>app>setting>surveys>surveys.html/surveys.editor.directive.js

@rowasc
Copy link
Contributor

rowasc commented Oct 10, 2020

So this will require changes in the API code, not the frontend. Would that be something you are still interested in? If so, you'll need to modify the migrations/20150904021011_add_default_post_type.php so that it reads "Untitled survey" instead of "Basic Post".
Note that this will only affect new deployments, so to test it, you essentially need to "re create" the database through the migrations to ensure they work as expected. I can help/guide you but let me know if you don't want to do backend changes and I'll un-assign .

Meta note to everyone: while yes typically you wouldn't want to modify a migration, in this case this migration specifically runs for deployment creation and I do not feel we should add a migration because it would affect existing users of the platform (who may be perfectly happy with "Basic post" or would be confused if we change it in their existing deployments)

@muchirijane
Copy link
Contributor

Hey @rowasc, I am still interested. I have seen the code in the file thank you. I would appreciate your help in the testing process of the code. How do I get started with "re-creating" the database?

@rowasc rowasc removed the Community Task Issues that the Ushahidi OSS community is encouraged to contribute to label Oct 12, 2020
@rowasc
Copy link
Contributor

rowasc commented Oct 16, 2020

Hi @muchirijane
I'm not sure if I already answered by email, but just in case: you do so by dropping the database locally, then re-running the migrations
Basically drop the database locally (you can do this through the mysql cli, inside vagrant) then run the migrations again with composer migrate .
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants