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

Various issues around similar tagnames, powertag listings vs. core tag listings, and possible redirects #3246

Open
ebarry opened this issue Aug 21, 2018 · 8 comments
Labels
break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration discussion

Comments

@ebarry
Copy link
Member

ebarry commented Aug 21, 2018

Please describe the problem (or idea)

What happened just before the problem occurred? Or what problem could this idea solve?

I was navigating around the hydrogen sulfide research area from https://publiclab.org/hydrogen-sulfide and clicked on the power tag, and through clicking the link i arrived at: https://publiclab.org/tag/question:hydrogen-sulfide

At first i was concerned that the lead wiki wasn't showing up, as it does on the regular tag page https://publiclab.org/questions/tag/hydrogen-sulfide.

Upon further consideration with @steviepubliclab , we realized that the issue is something else entirely: content-type power tags should not have their own tag pages.

Our suggestion is that it would be better to redirect tag pages for content-type power tags such as question:CONTENT to the regular tag page for that content: https://publiclab.org/tag/CONTENT.

What did you expect to see that you didn't?

At first i expected to see the tag page have a lead wiki page, but then i realized i was in a completely useless view of a power tag tag page.

Please show us where to look

https://publiclab.org/hydrogen-sulfide
https://publiclab.org/questions/tag/hydrogen-sulfide
https://publiclab.org/tag/question:hydrogen-sulfide <-- this is the URL that should redirect to the one above ^^

What's your PublicLab.org username?

This can help us diagnose the issue:

liz

@ebarry ebarry added this to the Tagging and topics milestone Aug 21, 2018
@ebarry ebarry changed the title Idea: redirect tag pages for content-type powertags to regular tag pages Idea: redirect tag pages for content-specific powertags to regular tag pages Jan 2, 2019
@ebarry ebarry changed the title Idea: redirect tag pages for content-specific powertags to regular tag pages Redirect tag pages for content-specific powertags to regular tag pages Jan 2, 2019
@ebarry
Copy link
Member Author

ebarry commented Jan 2, 2019

@publiclab/connectors , could you please help by providing a link to the relevant line in the code? Thanks!

@jywarren
Copy link
Member

jywarren commented Oct 7, 2019

Hi, I'm adding the add-code-links label to this, but i also had some follow-up questions.

I can think of some uses for tag pages for power tags; one I just used was http://publiclab.org/tag/with:warren, to see all posts I've made. It could also be useful to see all microscope activities with http://publiclab.org/tag/activity:micro - so I am wondering if it's a more generalizable solution to:

  1. have the tag card at the top of a page like this say, briefly, something like: "This is a [power tag](...). Also see content for [hydrogen sulfide]."

  2. Or, we could have the page display wiki content from the simple "core" tagname, rather than the power-tag version, so:

http://publiclab.org/tag/activity:micro would show the tag card image and text preview from http://publiclab.org/wiki/micro instead of http://publiclab.org/wiki/activity:micro

Of these two options, do you like either more than redirecting all power tag tag pages to their "core" versions, so as to address the potential usefulness of /some/ power tag tag pages?

Thanks!

@jywarren jywarren closed this as completed Oct 7, 2019
@jywarren jywarren reopened this Oct 7, 2019
@ebarry
Copy link
Member Author

ebarry commented Nov 14, 2019

HI @steviepubliclab and @publiclab-mimi , can you check this suggestion that Jeff made about how to direct powertag pages back to the main tag page?

@ebarry ebarry modified the milestones: Tagging and topics, API Nov 14, 2019
@steviepubliclab
Copy link
Contributor

Given our move to hide powertags, this might be less of an issue. People wouldn't be presented with powertags to click upfront right?

@stale
Copy link

stale bot commented Oct 7, 2020

Hi 😄, this issue has been automatically marked as stale because it has not had recent activity. Don't worry you can continue to work on this and ask @publiclab/reviewers to add "work in progress" label 🎉 . Otherwise, it will be closed if no further activity occurs in 5 days -- but you can always re-open it if you like! 💯 Thank you for your contributions 🙌 🎈.

@stale stale bot added the stale label Oct 7, 2020
@ebarry
Copy link
Member Author

ebarry commented Oct 7, 2020

This will be less of an issue, but still something we should address so people don't "get lost" in our plumbing.

@stale stale bot removed the stale label Oct 7, 2020
@ebarry
Copy link
Member Author

ebarry commented Jan 12, 2021

So progress has been made here, but i believe the "wires are still crossed".

https://publiclab.org/tag/micro looks like this: 0 content

Screen Shot 2021-01-12 at 3 55 43 PM

https://publiclab.org/tag/activity:micro looks like this: 0 content

Screen Shot 2021-01-12 at 3 58 19 PM

https://publiclab.org/wiki/micro looks like this: a proper main page
Screen Shot 2021-01-12 at 3 59 04 PM

https://publiclab.org/tag/microscope looks like this: 64 Research Notes, 25 Questions, 2 Wikis but no lead image:
Screen Shot 2021-01-12 at 3 59 55 PM

https://publiclab.org/tag/microscopes has 29 Research Notes, 26 Questions, 4 Wikis
Screen Shot 2021-01-12 at 4 01 11 PM

https://publiclab.org/wiki/microscope is a redirect that only mods and admins see:
Screen Shot 2021-01-12 at 4 03 07 PM

@jywarren
Copy link
Member

Hi all, just noting i think we still need to come to a decision on whether option 2) from the above comment is a good way forward? Given that we've identified possible uses for pages like these as also described in that comment above.

To the screenshots Liz has posted in the last comment, I can see there may be some possible ways to reduce confusion for users, but am not sure if either redirects or mirroring the main image and "card" text are the right solutions. Also, there are some additional observations about pages with similar URLs, but that don't have a powertag/tag relationship like activity:micro vs. micro -- rather, they are just very similar to each other, like micro, microscope and microscopes. So that seems like it may need a different brainstorm of solutions altogether.

One possible solution for the "no results" on pages like https://publiclab.org/tag/activity:microscopes is to have the code around the no results message try to detect if there's a colon in the tagname, and suggest the "simpler" core form. So if it shows no results but the tagname is activity:microscopes, it might have an extra message like: Try looking under just /tag/microscopes or something.

Finally there is one of the original observations that still exists although I'm not sure if it's a problem; these two very similar pages: https://publiclab.org/questions/tag/hydrogen-sulfide vs https://publiclab.org/tag/question:hydrogen-sulfide

So this now looks like it may need more discussion in detail as well as to be broken out into 2-3 or more sub-issues for these various scenarios and solutions. Thanks!

@jywarren jywarren added break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration discussion labels May 18, 2021
@jywarren jywarren changed the title Redirect tag pages for content-specific powertags to regular tag pages Various issues around similar tagnames, powertag listings vs. core tag listings, and possible redirects May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration discussion
Projects
None yet
Development

No branches or pull requests

3 participants