ctacdev / social-media-registry Goto Github PK

Should be namespaced as:
/api/v1/{data_type}.json?query_params
specific resource
/api/v1/{data_type}/{id}.json

Should attempt to match https://github.com/WhiteHouse/api-standards as best as possible

For reference:

The mobile apps form is missing many attributes, including version details

The goal should be to keep this updated as we make edits to the application. We could set up multiple pages, but just the one makes it easy to hit ctrl/cmd + f and fine what you need. Should include documentation on how services work (and how to add one).

Should we prune the old controllers and views, or should we keep them for reference? Currently most of the functionality has been replaced.

Swtich to a panel based view (bootstrap panels)

Each panel should have the full information of the social media registration (similar to the show view).

Each panel should have a restore button to restore the item to that state.

Right now it contains a collection of mobile app and social media outlets. Need to figure out a way to store whether that item is currently published or not, and update these records to point to the right place.

Examples, being able to specify children tree for agencies (is this worth anything).

Should there be queries to get the list of languages, list of platforms for mobile, any other data?

Is there anything missing?

Add an interface to add/remove registrations to a gallery.

Several of the controllers are not properly filtering the parameters (mostly due to copy/pasta).

What do we need to do? Just add papertrail to join tables (I think this is the case actually).

Will roll our own tables, and remove the dependency on this gem. Though useful, the polymorphic nature and lack of insight into the functionality could make it a problem down the road for O&M (especially for outside developers).

boxer is outdated, switch to using jbuilder views.

Complete the social media show view, to ensure looking at an item gives a complete view of the items information.

These will be people that will be messaged when a item is modified, placed under review, archived, destroyed, or other. We will add an interface to message all contacts related to an item.

Maybe this should be a discussion piece to make sure we do this the right way.

Include information such as groups, user, agency, and other fields. Groups should not be editable, as this comes from OMB max.

research capabilities to do multi model search. currently may not be supported well, may have to use solr/elasticsearch adapter directly.

For now, we can do some like queries and generate JSON, but we will not have any ties to models directly with that methodology (at least, not without some hijinx).

Each user should have an "email this user" box, to allow email from in the interface.

This will do a few things.

Add a new records to a database table called email_messages (Class EmailMessage). It will then use activejob to queue a worker to send the email. Users should always get a copy of the email they sent, so that a conversation can occur with the reply all.

database columns

to: comma seperated list of email addresses
from: current_user (link)
message_body: textual message body

Main goals: learn active job! http://edgeguides.rubyonrails.org/active_job_basics.html

Some recent changes have made it less clear the difference between mobile app versions on screen. Perhaps we can also condense each version into a smaller block overall.

This should return a JSON document that will be used to configure a front-end swagger in the public directory for embedding on various sites.

It'll be responsible for returning documentation for each version of the api.

For mobile apps and agencies, the = version.reify doesn't assign the correct entity to the variable.

Looking at include jquery token input
http://loopj.com/jquery-tokeninput/

for agencies, tags, and contacts tied to social media accounts / mobile applications.

do you see any issue with that stylisticall @srudra. do you have any preferences in tokeninput plugins?

Headers should be clickable to sort the data. They should indicate sort direction with arrows!

create some demo pages (with demo javascript in swagger-test-site)