Filter users who do not have good reputation

fix wiki
fix all apps dependent on this api

• fix self
• fix cw portal

Currently the reach is dismal. Find a way to beat it.

When the user is reporting a new item that has been lost/found, show a tooltip of matching items. Clicking on any item should open a modal showing the information of that item, with an option to resolve it then and there.

Jaldi se bana de!

Add a search field (maybe front end / solr) to search for lost / found items.

Currently the app gives more preference to reported lost items while rendering them on the map. Remove this priority and instead render the most recently reported items on each location, regardless of whether they have been reported lost or found.

Polish the final look before deploying.

• implement ajax
• Improve forms to render error on the same page
• Add descriptions to fb page
• Don't allow dates later than today in the client side as well
• Change date format. example "5 days ago, a month ago".
• Allow the main page to be open for all.
• Don't remove items.
  • Mark them as claimed
  • Show claimed items differently on the map
  • Change email requesting people to remove their item from the list of items found / lost.
  • modals for confirmation
• Add google analytics
• change maps rendering to client side js
  • also add confirmation modals
  • also link for viewing images
• Attach image, view image button
• Remove priority
• Add comments to code
• send mails asynchronously
• post to fb asynchronously
• Make a feedback page
• Don't let markers overlap
• Refactor js
• allow only IIITD accounts

Redirect the website through Byld Server.

Clicking on one of the map markers should close any other open pop up descriptors.

Maybe solution: replace all the '\n' occurrences.
Adding multiple lines messes up with the rendering js code which accepts arguments.
Please look into this. I too will try to solve this

I'm uncertain of the current distribution approach (over a Facebook page) as an effective method.
I believe its time to re-consider how to broadcast this information.

Thought: Maybe a widget on the connected-to-gateway tab? The API could be used for that.

cc: @IIIT-Delhi/byld-admin
You might be a better position to find a better contextual solution.
I'll be happy to help with any onboarding.

The username is set as a readonly hidden form field. Remove it and add the user in the back before saving the form, to prevent malicious POST data. Refer to this answer.

Shift the method of processing the front page. Rather than processing on every request, render it at signals of change in items, and simply render the cached page at requests

The date format in the map marker is in yyyy-mm-dd format, I think it would be better to keep in dd-mm-yyyy format.

I checked the all items list. New lost/found items facebook posts are missing again.

CW portal example of 404 Api is not working.

• Tabs for lost and found items
• Improve the home page
• Made with byld 😜
• Make navbar like this
  • Navbar - All items, Facebook Page, About, FindMyStuff API
  • Navbar- All items, Facebook Page, About, Sambhav (History, FindMyStuff API, ,Give feedback, Logout)
• Refactor everything using base templates
• Add details in api page
• improve history / inventory page
• don't make the home url as gmaps, but keep it root
• correct team page

Please show the person name and email-id, must required.

• Map default - satellite with labels
• Buttons for report lost/report found on the map
• Make the size of the markers slightly smaller - check for congestion again. decide between 3 or 5.
• Change colour of found marker
• Make the markers static
• improve the font setting in the popup

Remeber to add new locations

When the portal opens and people start using it, there might be a lot of congestion of markers on the map. Maybe we could have different colours for lost / found items (maybe blue/red or green/red).

Message contents : "There was something wrong in the information provided."

The findmystuff site is down.

• Get token to page with infinite rights
• Shift to multiprocessing

Instead of limiting to 10 markers on map, should we do max of 3-5 markers per place ?

Refactor and send jss and inline css to external files

When a quantity parameter is also sent while asking for the search results from the API, if the quantity asked for is more than the total search results, the returned quantity parameter is wrong.

In the items' database fields, the location is stored as the strings (names of the locations). Shift that and use one-to-one keys. The task is not really hard per se, however you might have to go through the complete source code in order to identify possible problems caused due to shifting.

My 404 Apps Tab ideally shouldn't be in the user profile as every user might not be a developer, I think it would be better if we can create a seperate app registration for the developers and not mix with the current profile.