This is a testing site only. See the live Public Lab site here »

# Power Tags

This is a revision from September 11, 2019 14:57. View all revisions

« Back to Authoring Help

Power tags are an advanced feature which can add extra functions and layout options to your wiki pages (and sometimes research notes). They are entered like regular tags but follow the format key:value. After adding a power tag, you must refresh the page.

To add tags, look for this box at the bottom of a wiki page or research note:

### General power tags

• events:foo displays a listing of research notes tagged with "event" and "foo", and a link to post new notes with those tags in the left sidebar.
• sidebar:featured displays "featured" links and images in the sidebar instead of the usual "related content"
• sidebar:none hides the sidebar
• style:presentation hides the wiki toolbar (with Edit, Talk, Revisions) for more formal pages, and makes the lead image of wiki pages full-width
• style:minimal just hides the wiki toolbar (but it's accessible via a small caret button)
• style:wide removes the 800px width limit from wiki pages, and allows them to flow full page
• style:fancy is used to style articles from the GrassrootsMappingForum
• style:nobanner
• parent:foo adds a bar that links back to a parent wiki page
• with:username adds a co-author to your research note with a live link to the user's profile page, however, the note itself will not show up under that user's profile.
• lang:es or iso:es is the way to indicate language in a research note or event. In this example, es indicates Spanish.
• locked -- locks a wiki page from edits except to moderators and admins. An atypical power tag in that it doesn't follow key:value format; documentation here
• redirect:____ -- redirects a page to the page with the specified ID -- i.e. redirect:100 would redirect to node 100. Does not affect admins or moderators.
• series:____ -- displays a message of "This is part of a series on tagname." with a link to /tag/tagname
• abtest:____ – redirects 50% of page visitors to the page of id given, such as abtest:1234 -- for "user testing" two versions of a page. Admins and moderators not affected.
• activity:____ -- will list the content in an activity grid set to that tag
• question:____ -- will list the content in as a question on that tag page
• alert:___ -- will show the feature as alert on that node.

### List of power tags useful for project or location based pages:

• lat:41.023 and lon:-71.023 latitude and longitude. Together with the simple tag "chapter", the combination of these three tags will create a point for your chapter on the Places map
• events:foo displays a listing of research notes tagged with "event" and "foo", and a link to post new notes with those tags in the left sidebar. Especially useful where foo = the name of your chapter page.
• list:foo displays recent posts from a Google Group with the name "foo" and a subscription input box
• tabbed:notes and tabbed:wikis display a tabbed header which offers tabs with links of related research note and wiki content
• notes:foo displays 4 recent "popular" research notes tagged "foo" (in grid view, popular means >20 views) at the top of the page, under the tabs if they exist. For example see [Gulf Coast](/wiki/gulf-coast]
• parent:foo adds a bar that links back to a parent wiki page, especially useful for places within regions

You can display alerts using power tags. Admins can create new types of alerts which can be displayed on any wiki or note. An example is alert:testing-2 -- use this tag on your page, and you'll see an example alert appear at the top of the page content (below the title).

Available alerts using this system are:

• alert:testing-2
• alert:

Admins: to create new alerts, create a new Feature with the name alert-_____ where the blank is the alert name. For example, for the tag alert:testing-2, the feature is named alert-testing-2. The text of the Feature must include the "alert" HTML too:



Notice This is a test.



### Inline power tags

You can now use "inline" power tags in the middle of a research note or wiki page. The first one is for generating a list of notes for a given tag, and is used in this format:

[notes:<tagname>]

For example, to list all notes tagged with peru, you can use:

[notes:peru]

Wiki pages can be listed too:

[wikis:coqui]

To create a button with text on top that links somewhere outside of publiclab, use:

[button:foo:https://www.google.com]

The above creates a button with a "foo" on top of a button that links to Google. For a button that links somewhere on the site, you can use something like:

[button:foo:/questions]

The above creates a button with the text foo on top that links to: "[link you are currently on, you can find this on your address bar]/questions". So if I'm on https://publiclab.org, this links to https://publiclab.org/questions.

For a more complex example, you can list all questions on the topic of "infragram" using:

[notes:question:infragram]

More advanced uses like activity grids can be found in this post:

https://publiclab.org/notes/liz/08-30-2016/check-out-these-activity-grids

And in the requesting responses documentation.

### Inline People Lists

[people:organizer] -- will display any people tagged as organizers. Add profile tags on your profile page (admins can do this for anyone)

Example:

warren
cindy_excites
eustatic
zengirl2
marlokeno
pdhixenbaugh
sarasage
shanlter
LauraChipley
vanshika421
abhijeet2
Mustapha

### Inline Maps

Maps may be embedded inline, displaying content tagged with lat:___ and lon:___ location tags. Read more about inline maps here.

### Inline graphs

This feature is still in testing, but allows display of a CSV file as a graph:

[graph:/i/25356.csv] will display:

CSV

### Prompts

Prompts let us offer a place on a wiki page where a reader can enter text and it's directly inserted into the text of the wiki page just above the prompt.

[prompt :text:Placeholder text] (without space after prompt)

That looks like this when saved:

[prompt:text:Placeholder text]

We can also ask for longer-form text input with the keyword paragraph -- but be aware that the "placeholder text" can only hold letters, numbers and spaces -- no punctuation (yet):

[prompt :paragraph:Placeholder text] (without space after prompt)

That looks like this when saved:



[prompt:paragraph:Placeholder text]

Two identical prompts on one page can cause trouble, but if you add a unique id, you can get around that:

[prompt :text:Placeholder text:UNIQUE-ID] (without space after prompt)

The prompts are better documented here.

There's also this type of "edit here" prompt:

[ edit ] (but without spaces)

Which generates this type of prompt:

to help complete it!

### Automated power tags, not for manual adding

You might see some of these being generated automatically, like when checking the box for a Research Note to be an "Event" or a "question" or when awarding Barnstars to someone's Research Note. Don't manually add these:

• event:rsvp date:YYYY-MM-DD rsvp:username
• barnstar:barnstarname
• question:foo response:foo

### Tag aliasing

We've created a system for aliasing tags, which serves a number of purposes:

A) disambiguation -- we have both spectrometer and spectrometry -- as of recently, we'd prefer spectrometry. So we make each the alias of the other, and the two become somewhat (but not completely) interchangeable on the site.

1. When looking at https://publiclab.org/tag/spectrometer, you see content tagged with spectrometry, and vice versa.
2. Email notifications do not yet take advantage of aliasing, but may at some point (see below).

B) subcategories -- multispectral-imaging contains and is broader than infragram.

1. When looking at https://publiclab.org/tag/multispectral-imaging, you should see content tagged with infragram.
2. When looking at https://publiclab.org/tag/infragram, you should NOT see content tagged with multispectral-imaging -- your query is more specific than that.

Later goals:

Some aliasing features are more complex and not complete yet.

Email subscriptions - when people subscribe to a tag, they should receive emails when content is posted using a tag that is a (more generalized) alias of the subscribed-to tag.