mapstory / mapstory

MapStory is the free atlas of change that everyone can edit

MapStory

MapStory.org is the free atlas of change that everyone can edit. We are a community, not a company, working to organize humanity’s shared knowledge about how the world evolves geographically over time, and to make this knowledge easily accessible as an open educational resource.

The MapStory community’s work breaks down into 3 big tasks. We call them the “3 Cs”. First, once you’ve created a profile, you can collect spatio-temporal data and import it. We call each dataset imported into MapStory.org a “StoryLayer”. Second you can compose MapStories that provide nuanced understanding of historical change by combining StoryLayers and other narrative elements, like images, text, or video. Finally, you can curate the accuracy and quality of content presented in MapStory.org by adding ratings, checking metadata, making comments and committing version edits to the actual StoryLayers themselves, much like you might edit a Wikipedia page.

Getting Started

Prerequisites

This guide assumes you are using a UNIX based operating system such as Linux or OSX and have the below installed.

git
docker
docker-compose
gmake

Setup a Development Environment

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. Start by forking the mapstory repository to your own Github account, and then cloning that repository to your local development environment.

git clone https://www.github.com/<your-username>/mapstory

Add the following to your /etc/hosts file

127.0.0.1       docker
::1             docker

Run the following commands in the checked out git repo to start up the docker containers.

git submodule update --init --recursive
make pull
make up

Your local site should now be available at http://docker/.

Additional information about using the docker build is available at our Docker README.

Built With

• Python 2.7 - The primary backend development language.
• Django 1.8.7 - The back end web development framework.
• AngularJS 1.6 - The front end web development framework.

Contributing

Please read How to Contribute for details on our code of conduct, and the process for submitting pull requests to us.

Styleguides & Best Practices

Please review our Contributor Guides for best practices and style guides before contributing to the project.

mapstory's Issues

Add the `geonode_authorize_layer` function to the build.

https://github.com/ROGUE-JCTD/rogue-cookbook/blob/4f2ed83f046ecb26a74f456a9ea1463f1f392f77/recipes/database.rb#L67

Fully collapse sidebar into hamburger menu

Currently, the viewer sidebar collapses to the LEFT, and partially shows. The ideal behavior is for the sidebar to fully collapse, and to be accessible by clicking the hamburger menu at top left.

Redesign and reexamine notifications in Composer

• We need to evaluate positioning collisions with loading/notification toasts, legend (currently uses “Toaster”, open to modifying or building custom solution)
• Nothing currently exists for this, would be custom built, otherwise no technical feasibility concerns
• Might need to re-evaluate Toaster library and how notifications work

Resize and compress images to improve load times

Resize and compress the images from the following lists:

https://mapstory.org/admin/mapstory/sponsor/
https://mapstory.org/admin/groups/groupprofile/

This will improve load time across the site. cc/ @emilyashley

Design "preview mode"

Add "preview mode" toggle to the header and design any user flows surrounding that.

Composer redesign: Notifications

Redesign notifications. Some scenarios to account for:

• "Are you sure you want to leave this page?" if autosave hasn't taken place
• "Loading" messages/toasts regarding layers and basemaps
• Error in validating of a form (user forgot a required field or entered invalid info into a form)
• Evaluate positioning collisions with loading/notification toasts & legend
• error saving
• success saving
• error publishing
• success publishing
• loading for saving
• loading for publishing
• Success in deleting a chapter/layer/pin/etc.
• Failure to auto-save
• loading for deleting a story
• loading for discarding staged changes
• loading for unpublishing
• error deleting a story/draft
• success deleting a story/draft
• error discarding staged changes
• success discarding staged changes
• error unpublishing something
• success unpublishing something

Redesign Viewer Sidebar: Chapter summary

Currently the chapter summaries can be quite long and require the user to scroll in order to see the full description. If the summary is long and the user must scroll, the "next" and "previous" links aren't initially visible.

Things to consider as part of this effort:

• Should there be a character limit on Chapter summaries?
• Should chapter summaries for sidebar be different than chapter summaries for details page? (i.e. should they be two separate fields in Composer -- sidebar text vs. detail text)
• "Next" and "Previous" should be visible without scrolling

Remove hopscotch tour from composer

It is now out of sync given new CSS.

@glynnis new composer interface will include an updated method of guiding new users in composer.

Viewer Redesign: Sidebar as a canvas for StoryPins

When a user views the story sidebar, the only thing that currently displays is the chapter summary.

Explore design possibilities of using the sidebar as an option for displaying StoryPin content -- an alternative to showing pins on the map or the timeline.

Create site map

Reimplement carousel for featured MapStories on Homepage

A moving carousel allows us to show off a set of mapstories on the homepage.

If the implementation is easier without the category tabs, we can remove those and just feature a single common set of mapstories.

restatement of MSSS-284 in Jira, https://issues.boundlessgeo.com:8443/browse/MSSS-284

Table of Contents: Design "Add New Chapter" state

Current state: "Add New Chapter" button drops you into the "chapter info" tab. Is this what we want to maintain?

Complete StoryLayers tab design: Styles/Masks

User Story
As a user composing a story
I want to apply custom styles to a layer within my Mapstory (without affecting the layer itself)
In order to emphasize events or places and help viewers understand the narrative of my MapStory

Acceptance Criteria

• Include Icon Commons in the styling panel
• Understand and apply logic from the current implementation of the styling panel for any styles that should be conditionally displayed based on layer type, etc.
• Represent masks (if needed separately from Legend masking?)

Deliverable
Incorporate styling features into the high-fidelity mock-up for Composer MVP to facilitate discussion about technical feasibility with the team and create feature stories that further refine the design or technical tasks associated with this.

Provide valid uploadable data as a test fixture

amongst challenges of trying to set up mapstory is that there are no data sets easily accessible and documented in setup instructions to test the install end to end.
These should be able to double as test fixtures for uploading (and extended functions).

Composer Redesign: Tour

• Tour of composer, we could convey this current copy about where to find drafts
• Current tour

Can't update thumbnails after initial change

After first uploading a custom thumbnail, consecutive thumbnail changes don't apply.

hyperlinks in News Items text?

Is there a format for creating hyperlinks in the text of a News Item?

Propagating upload errors

Failure in the importer causes a problem - the underlying problem is masked:
GeoNode/django-osgeo-importer#4

Adding it hear even if its a uploader concern because it impacts, and I suspect there should be tests in the mapstory layer to make sure things work.

Not sure what happens if a problem fails in mapstory-specific tasks - (i cant get importer to succeed the mapstory part of things yet - fails without any message or log somewhere after setting up geoserver layer)

Will also submit issue re having test data that definitely works available as a test fixture.

Finalize design for Chapter Info tab

Finalize design for "Edit story data" modal (from header)

Where does the information in the story properties modal display?

• Title: story detail page, embedded story, explore page
• Summary: story detail page (could be added to explore or embedded viewer but not currently there)
• Tags: story detail page, tags make a story searchable, add checkbox for "Include tags from all layers", add autocomplete functionality
• Category: story detail page, explore page, on the homepage if it becomes featured since the features are separated by category
• Location: not currently displayed anywhere, "include all regions for layers", autosuggestions based on tree (i.e. "Honolulu" recommends "Hawaii" and "United States")

Finalize design for Chapter Playback settings

• Can default chapter zoom be combined somehow with StoryFrames so that the presentation of both is simplified and a better experience for the user?
• Since aspect ratio issues are the same for StoryFrames and Chapter Zoom, use the same cropping mechanism for both.
• Communicate to the user that setting a chapter zoom is a requirement, or communicate somehow what default will be assumed (so that it's clear that they need to set one). Or do we try to understand where the data is and center around the data as a default?
• Determine whether cumulative and range are part of the Composer Redesign MVP

Example Map in Get Pages module

The example map form in Get Pages seems to ask for too much information. Is it possible here just to add a hyperlink to a mapstory?

Share mock-ups for MVP and review with the team

Ensure that mock-ups cover all features necessary for MVP and don't represent any features that won't be included in the initial release. Vet them with the team and publish them/break them into issues here.

Add a clear search function to explore

Currently there is no simple way for a user to return to a state where they can see all StoryLayers and MapStories after they have filtered content somehow, using a filter or word search, for example. The only obvious way is to refresh the entire browser.

A Clear Search button will make it easy for a user to return to a state of seeing all content.

this is a restatement of MSSS-251 https://issues.boundlessgeo.com:8443/browse/MSSS-251

Icon Commons icons should show in a list without requiring search

When a user is trying to add an icon to a point-layer style, the Icon Commons modal appears with no icons pre-loaded. Thus, it looks empty:

If a user knows what icons they are looking for, they can type in a keyword and have icons appear, but this requires already knowing what is there, something very few users will no.

Instead, the Icons Commons modal should appear with all icons pre-loaded into the modal so the user can see them. The text box to enter keywords should just function to reduce the Icons that appear to those that correspond with the Keyword (in other words, a filter).

Add templates, JS list, and other data to site map once added to wiki

Once the site map is relatively complete, create a wiki page that lists JS, assets, templates, and any other relevant info for each page.

Make a grid of story states

This story needs to be completed before #275

What states can a story be in with regards to being published, unpublished, draft, saved vs. unsaved changes, etc.

Prep these states, discuss with @jonpmarino and @glynnis so that Design for the header can be completed.

• Finalize with Marino what states a story can be in:
• • Can users unpublish/withdraw a story?
• • If a user chooses to make changes to a published story, what options do we present them? Unpublish the story while editing then republish vs. create a draft that will overwrite the published story when republished
• • Can users discard a draft (of a previously published story)

@jonpmarino,

StoryLayers can be:

• draft: only viewable by the owner from his/her profile), or an administrator (this should be rare, perhaps as a preview when first uploaded, or if there is a problem. Low priority)
• public: viewable in the search by any visitor to mapstory.org (StoryLayers should be public by default)
• community editable: any registered user can contribute edits to the storylayer (a layer has to be public to be community editable)
• not community editable: only the layer owner can contribute edits to the storylayer. A layer could be "not community editable" in draft or public mode.

MapStories can be:

• Draft - only viewable by the owner from his/her profile), or
• Published - viewable by any visitor to mapstory.org site

NOTE - Returning a mapstory to 'draft' unpublishes the story until it is re-published
NOTE - MapStories can only use public StoryLayers since, by definition, a layer has to be public in order to be viewed and shared in a published mapstory.

(It looks like when a MapStory is "returned to draft" it successfully is hidden from explore, but can still be accessed with a direct link)

(It would be nice if the user in composer was given more detail about what happens when "saving as a draft", as they are when a story is published)

Remove storyteller explore filters until they are functional

The "interests", "city" and "country filters on storyteller explore don't work and should be removed from prod until operable.

(this is a restatement of MSSS-248 in Jira, https://issues.boundlessgeo.com:8443/browse/MSSS-248

Re-deploy Activity Feed to user profiles

We de-activated the Activity Feed on user accounts because:

1. it was showing the creation of individual "chapters" as its own action, with links to chapters outside the context of their story and,

2. we weren't tracking users uploading of icons in the activity.

We should add the icon uploads to activity feed data and remove links to individual chapters, rather than just mapstories, and redeploy activity feed to user profile

Acceptance Criteria:

-Activity Feed added back to user profiles
-Chapters not showing up in activity feed w/ links outside the context of their story
-Icon commons uploads reflected in activity feed.

The `restart django` task fails on first run.

The restart django task attempts to restart django before it has been started. I can temporarily fix this by changing the state to started here: https://github.com/MapStory/mapstory-geonode/blob/master/scripts/provision/handlers.yml#L10. I'm sure there is an easy way to add some conditional logic here.

NOTIFIED: [restart django] **************************************************** 
failed: [192.168.56.151] => {"failed": true}
msg: FAILED: attempted to kill gunicorn-django with sig SIGTERM but it wasn't running
gunicorn-django: ERROR (already started)

transparency of viewer sidebar is too high - text not legible if strong styles are applied

the current viewer sidebar has a transparency setting, so that the map, layers and styles are visible behind Chapter Info text. The current setting is too transparent. Text is difficult to read if strong stylers are applied.

In screenshot below, the line styling on the States is strong, and makes text difficult to read.

Research different settings based on different styles and apply fix.

Add Wikipedia as a whitelisted service for StoryPins

Design playheads feature for selecting date

Add playheads feature/UX to:

• StoryPins
• StoryFrames

MapLoom build missing steps

To get MapLoom to build correctly, you currently have to enter the MapLoom project and run:
bower install
npm install
grunt copy

New mapstories have no initial thumbnail created

We are not generating any original thumbnails for new stories anymore. All appear as an empty image.

A first effort model could be to grab the image at the last slice of Chapter 1. This will guarantee that there is some data features to visualize. And, every story will have 1 chapter.

Users can already also upload their own thumbnail to override the auto-thumbnail. But we need to at least provide one to start.

In the future, it would be cool to have an auto animated-GIF generator that takes a number of slices from the story.

(This is a restatement of MSSS-280 https://issues.boundlessgeo.com:8443/browse/MSSS-280)

Finalize design for StoryFrames tab

Acceptance Criteria

• Remove playheads and add back date fields
• Add active highlight to indicate which StoryFrame is active on the map
• Add header message like StoryPin to indicate active storyframe (and move directions there)
• Make improvements to StoryFrame text so that the user better understands that the viewer won't see the grayed out/cropped view that they do as they're creating the frame ("Click and drag to resize and set the StoryFrame position on the map. The zoom and StoryFrame you set will override this chapter’s default.")
• Where does the title and text for a StoryFrame go to? i.e. where does it appear in the MapStory detail viewer? Figure out how to communicate this to users in the question mark text. If we allow StoryPins to appear without a geographic context, do StoryFrames need any additional information? Ask Marino about this and understand scope of the StoryPins without geographic info.
• Write question mark text.

Deliverable
Incorporate styling features into the high-fidelity mock-up for Composer MVP to facilitate discussion about technical feasibility with the team and create feature stories that further refine the design or technical tasks associated with this.

Finalize design for StoryPins tab

User Story
As a user composing a story
I want to create StoryPins for my Mapstory
In order to emphasize events, media, or places to provide more information and context to viewers of my MapStory

Acceptance Criteria/Questions to Answer

• Change playheads back to current date picker fields for MVP mock-ups
• Bulk upload screens: modal, success/error messaging
• What should the default playback options be set to? Something the user has set for previous pins? Should they all be off? On? “Apply to all” or “create new storypin with these settings?”
• Are ‘Show StoryPin on timeline’ and ‘Show StoryPin on map’ mutually exclusive? Can you have neither selected?

Deliverable
Incorporate StoryPin features into the high-fidelity mock-up for Composer MVP to facilitate discussion about technical feasibility with the team and create feature stories that further refine the design or technical tasks associated with this.

Git logic in the ansible scripts should be idempotent.

If the developer is syncing a folder between the host and guest vm, the ansible scripts will fail when trying to clone the mapstory repos. Those tasks (mapstory.yml lines 14:29) should only run when the path does not already exist.

This seems like pattern to check if a path exists. (from https://groups.google.com/forum/#!topic/ansible-project/ifi8_8FTKVo)

- name: Check if path exists
 stat: path=/etc/monit/conf.d
 register: check_path

- name: It exists
 debug: msg='Yay, the path exists!'
 when: check_path.stat.exists

- name: It doesn't exist
 debug: msg="Boohoo, the path doesn't exist..."
 when: check_path.stat.exists == false

Finalize design for Composer header

This story depends on #273.

• Designing for a story that has been published, but has additional changes in draft mode but needs to be "republished" to push those changes to their live story

User testing for StoryPins tab

1. Are multiple pins expanded simultaneously useful?
2. How do we handle media playback for pins that show at the same date and time (or if they overlap)?
3. Would you like a “apply to all pins in this chapter” checkbox for the toggle switches/playback options for each pin or “create new storypin using this as a template”?
4. What defaults would you expect for toggle switches when you add your first pin. What about when you add subsequent pins?
5. Does the user understand which pin is active on the map?

Add support for raster filed on import

As a user, I want to upload raster data, such as a print map or an aerial image, or sequence of images, into MapStory as a StoryLayer so I can do things, like, make MapStories that animate digital data on top of historic print maps or images.

Acceptance Criteria

• Support injest of a single geo-referenced image with a date
• Support injest of a zipped file with several images (mosaic) showing change over time

Notes
Previous tickets for raster upload on the old site:
MapStory/mapstory-meta#669
MapStory/mapstory-meta#1264

Various UI/UX Issues

Major:

• The “What” option under “Refine Search” section on the Explore page does not show any results
  Test URL: http://mapstory.org/search/?limit=100&offset=0&is_published&category__identifier__in=geopolitics&q=
• The “Where” option under the “Refine Search” section on the Explore page does not have any effect Test URL: http://mapstory.org/search/?limit=100&offset=0&is_published&q=&extent=-126.21093749999999,49.95121990866204,-104.0625,64.09140752262307
• Adding a tag causes a published map to become unpublished

Minor:

• Featured maps carousel on the homepage shows “No Featured Items in this Category” and template info before loading is complete
  Test URL: http://mapstory.org/
• Explore page shows "page 1 of NaN” before loading is complete
  Test URL: http://mapstory.org/search/?limit=100&offset=0&is_published
• The [email protected] email in the “Building a Better MapStory” message should be a mailto: or a contact form
  Test URL: http://mapstory.org/account/login/?next=/maps/new%3Ftour
  Parent div ID is “site_wide_announcements"
• Two different scrolling methods are used for the whole Explore page and the available StoryLayers. Maybe merge into one and consider infinite scrolling? This is a small point.
  Test URL: http://mapstory.org/search/?limit=100&offset=0&is_published
• The Explore page tries to load http://mapstory.org/static/lib/js/bootstrap-datepicker.js, but it gives a 404
  Test URL: http://mapstory.org/static/lib/js/bootstrap-datepicker.js
• “No Image” placeholder could be improved. Maybe a light grayscale map?
  Test URL: http://mapstory.org/static/geonode/img/missing_thumb.png
• Long titles overflow on the Explore page. Truncating and showing the full title on rollover is probably the best option.
  Test URL: http://mapstory.org/search/?q=Test&limit=100&offset=0&is_published
  Image:
  
• Keyword option on the Explore page is unclear and does not seem to function.
  Image:
  
• “Remember Me” checkbox is slightly misaligned. This appears to be a bug with default browser behavior on Chrome and Safari, though it is possible to override it with custom styling.
  Image:
  
• Labels under the StoryStyles section on the Compose page are cramped.
  Image:
  
• StoryBox editor on the Compose page needs alignment and text cleanup.
  Image:
  
• On the map preview page, it would probably be clearer to have “Save as Draft” and “Publish” instead of a publish/unpublish checkbox. The save button is also very low contrast.
  Image:
  
• Message for adding a keyword on the map edit page is missing a closing paren. Current text is "commonly used word(s) or formalised word(s) or phrase(s) used to describe the subject (space or comma-separated"

Finalize design for Map Control Settings

• Add toggle to show story description and title. Right now the embeddable viewer doesn't display this anywhere (the users would have to visit the detail page on mapstory.org). Do we want to add the story description somewhere in the embeddable viewer as part of MVP?

Expose keyboard shortcuts and mouse functionality to users for mapping contexts

problem w/ sponsors

Not able to add sponsors for some reason...

Normalize column names for imported data

When a user imports a dataset, the wizard should allow the user to help sanitize and normalize attribute names to a common schema so that there is consistency with naming and casing of attributes labels within the application. This will also help avoid the use of reserved words as attribute names.

We could keep a mapping of changes and use as future suggestions at the point of upload.

Example fields extracted from the existing database used for the time field however we shouldn't limit it to time fields:

A_year
Date_start
Elect_year
Expend_Yea
Fake_end
Fake_start
ISO_time
New_start
Oil_year
a_starting
a_year
a_years
aa_year
acc_date_t
access_days_time
acq_date
acq_time
active_year
activitystart
age_as_year
alt_year
amend
amended_by
amendscan
annexdate
anxyear
apprehende
ar_start
area_year
award_date
backend_start
bd_blends
beg_yr_as_year
begin_date
begindate_as_year
begindate_xd
begintime
begintime_as_date
begintime_parsed
begintime_xd
beginyear
beginyear_parsed
beginyear_xd
birthdate
bldg_end_d
bldgyear
blk_read_time
blk_write_time
buffers_backend
buffers_backend_fsync
build date_xd
byear
cal_year
can_year
card_date
cc_year
changeyear
checkpoint_sync_time
checkpoint_write_time
checkpoints_timed
class_date
closedate
codes_date
commentend
cowedate
coweyear
cowsdate
cowsyear
cpit_year
cpiy_year
creation_time
cy1year
cy2year
d1_year
d_years
data_end
data_start
data_time
data_year
date
date1
date2
date_
date_1
date_2
date_as_year
date_built
date_created_xd
date_end
date_end_1
date_estab
date_field_as_year
date_format_as_year
date_new
date_of_bi
date_of_st
date_rec
date_st
date_start
date_started
date_text
date_time
date_xd
date_year
date_yr
datebymont_as_year
dateend
dateended
dateform
dateformed
datenum
dateoftrea
dateonly_as_year
dateopened
dates
datestart
datestarted
datet
datetext
datetime
datetime_as_year
datetime_precision
datetimes
days_year
deededdate
deis_end
deis_start
depl_year
descendant
description_as_year
dispatch date / time
dro_years
e1_year
e85_blender_pump
e_date_xd
e_year
e_years
earn_year
ec_date
efayear
elect_year
encendido
end
end date
end date / time
end date_parsed
end date_xd
end year
end2
end2_parsed
end2_xd
end_2
end_acq_dt
end_chg_ty
end_date
end_date_1
end_date_2
end_date_2_as_date
end_date_3
end_date__
end_date_as_year
end_date_parsed
end_date_xd
end_day_
end_month
end_month_
end_mp
end_n
end_parsed
end_period
end_ref
end_rule
end_serf
end_slave
end_time
end_xd
end_year
end_year_
end_yer
end_yr
end_yr_as_year
endate
endcong
endcong_1
enddate
enddate_as_year
enddate_parsed
enddate_parsed0
enddate_xd
enddate_xd0
enddatet
enddayofye
enddesc
ended
endingdate
endlat
endlng
endlon
endofperiod
endofperiod_parsed
endofperiod_xd
endorsemen
endowment
endtime
endyear
endyear_parsed
endyear_xd
ent_date_as_year
est_crime_time
event_date
eventdate
exp_year
expend_cou
expend_dol
expend_obj
expend_sta
expend_yea
eyear
f_date
f_date_ope
f_year
fake_end
fake_start
fakeyear
fakeyear2
fats_end
fats_start
fcc_as_year
fdate_xd
feis_end
feis_start
final_time
final_year
finaldate
fipscode_as_year
fire_date_as_year
fire_year
fire_year_as_date
firstpumparriving_attendancetime
fiscal_date
fiscal_year
friendlyca
friendlyki
friendlywi
from_date
full_year
g_year
g_years
gdp_year
gender
gender_gap
gni_year
gpp_year
gps_time
gr_year
h_years
hdi_years
hl_year
homes_year
ht_year
i_year
identity_start
if_year
iit_end_da
iit_start_
im_year
image_year
in_end
in_end_ref
in_start
in_timeline
insert date_as_year
instdate
int_start
is_udt_dependent
iso_date
iso_end
iso_start
iso_time
isodate
isotime
it_year
iv_year
iyear
job_end_dt
job_start_
k_time
ktime
l_year
l_years
lat_end
lat_start
legal_date
legend
lending_in
listyear
ln_year
local_time
long_end
long_start
longitude_as_year
lv_year
lymet_year
m_year
ma_time
ma_time_as_date
ma_time_as_year
minde_year
mn2_year
mp_years
msndate
mt_year_
multimed_1
multimedia
n_end_date
n_start_da
n_year
name_as_year
name_start
neg_k_time
neg_time
neo_year
new_date
new_end
new_start
newdate
newtime
numbackends
numpumpsattending
numstationswithpumpsattending
observation date_as_year
oid_as_year
oil_year
on_year
on_year_as_date
on_year_as_year
opendate
openyear
osm_timest
osmtimesta
outdated
p1_year
p_years
pan_time
parent_end
parl_year
peak_attendees
pend_litig
permit_end
pg_dbt_end
pg_end_dat
po_year
prek_year
prepare_time
prsend
prsstart
py10year
py1year
py2year
py3year
py4year
py5year
py6year
py7year
py8year
py9year
q_start
query_start
rate_year_
ratif_year
rc_year
realdate
repdate
repyear
result_cast_datetime_precision
road_year
s_year
sale_date
secondpumparriving_attendancetime
self_time
sh_year
shift_time
showtime_
sql_language_year
sset_year
start
start date
start date / time
start date_parsed
start date_xd
start1
start2
startDate
startTime
start_2
start_3
start_as_year
start_dat0
start_dat1
start_date
start_date_as_date
start_date_as_year
start_date_of_incident
start_date_parsed
start_date_xd
start_ear
start_month
start_n
start_parsed
start_ref
start_time
start_value
start_xd
start_year
start_year_parsed
start_year_xd
start_yr
startcon_1
startcong
startdate
startdate_parsed
startdate_xd
startdated
startdatef
startdatefix
startdayof
starting_d
startingdate
starttime
startup_s2
startup_s3
startup_s4
startup_so
startyear
startyear_parsed
startyear_xd
str_year
study_time
sum_year
sum_year_1
sum_year_2
surveyyear
syear
synoptime
t1_year
t2_year
t5_year
t_year
taxyear
teen_year
tempend
tempstart
terr_year
time
time observations started
time1
time2
time_
time_as_date
time_as_year
time_e
time_hhmms
time_of_report
time_over_
time_parsed
time_perio
time_preci
time_precision
time_s
time_tab_1
time_tab_2
time_table
time_txt
time_xd
time_year
timeend
timeend_parsed
timeend_xd
timeline
timeline_1
timeline_Y
timeline_e
timeline_s
timeline_y
timeofcall
timeofftar
timeofobservations
timeontarg
timeseries
timespan
timestam_1
timestamp
timestamp1
timestamp2
timestamp3
timestamp_
timestamp_as_date
timestart
timestart_parsed
timestart_xd
timezone
tmp_end
tmp_start
to
to_date
total_attended
total_time
tracktime
typsend
u_starting
ur_year
usa__date
vending
vendor
vendorid
verbatimel
verbatimev
w12_end_yr
w1_opendat
w1_opendat_as_date
w1_opendat_as_year
w1_opendat_parsed
w1_opendat_xd
wendi_name
who_year
wind_year
xact_start
year
year1
year2
year_
year_1
year_12
year_12_13
year_12_14
year_12_15
year_2
year_adm
year_annex
year_appea
year_as_da
year_as_date
year_as_year
year_b
year_blt
year_built
year_close
year_compl
year_cor
year_date
year_draft
year_e
year_elect
year_end
year_end_as_date
year_est
year_found
year_id
year_insta
year_long
year_nu
year_of_im
year_open
year_opene
year_ord
year_parsed
year_parsed0
year_purch
year_s
year_st
year_start
year_start_as_date
year_t
year_tex_1
year_tex_2
year_text
year_txt
year_xd
year_xd0
year_year
yearalter1
yearalter2
yearannex
yearblt
yearbuilt
yearcensus
yeardbl
yearend
yearparcel
yearpassed
years
years_on_f
yearstart
yearstring
yeartext
yeartxt
yearval
yearyear
yearyear2
yearyear3
yr_ce_end
yr_end
yr_start
zone year
zone_end_y
zone_year
ztime

paver sync does not load initial_data fixtures

This results in the site tables not getting created and populated and results in a broken state. Specifically, when visiting any page, results in Exception Value: no such table: django_site

Add table columns in django-admin for MapStories like we have for StoryLayers

this enables bulk actions like setting categories or published status without having to into each MapStory one by one.

(not providing screenshots since an internal admin issue)

Smooth scrolling for parallax images

The home page now supports the parallax effect, however, if you scroll down the index page, it doesn't scroll very smoothly as compared to the homepage on MapStoryOrg repo . I'm not sure if that is an issue with the Smoothscroll.js file.

Use Core GeoNode

Remove all of the custom MapStory specific code from our fork of Geonode so that we can stay up to Geonode master, and so that the Geonode tests will work. Geonode is already fairly tested (and we can add tests and submit PRs to Geonode if anything is missing) so this will help get us a long way towards a high percentage of automated test coverage.