Project Posts

Project posts represent an individual project created by the end user.

#Fields and tags

Project Title

post.headline (field) Blog Title is used for Project Title

Project Description

post.content_before_flip (field)
Blog Content - stored in content_before_flip as this only requires a single API call

Project Post Tag

project_post
Tag to indicate the blog post is for a project - useful if looping through all users posts

Lat Long

lat_lng:LAT_LNG
map location lat lng - used to plot project location on map. Note underscore between lat and lng - NB tags can't have commas

Location

location:LOCATION TEXT
text address - suburb and postcode?

Status

project_status:STATUS
project status -affects project visibility on map. If the tag is project_status:Submitted then the project is not shown on the map

Author the blog post author (org)

Author Tag

author:AUTHOR_ID
also tag post with author (org) id - this can be useful if we need to find all orgs posts by tag

Project Author Tag

project_author:AUTHOR_ID
this tag is useful if we need to display all project posts for an author (org) by tag

Project Org Tag (optional)

project_org:ORG_ID
this tag is used for backwards compatibiity and clarity. If the user is an org this tag is also added - the ID will be the same as the author ID. It is used to show project posts on the org profile

Published State

post.status
If the blog post is not published it is hidden on the map

Category Tags

(See parent page for list)
Projects can be tagged with one of more Landcare WA categories which are used to filter projects on the project bank map