rahuldave / adsabs Goto Github PK

Mike wants a csv output of type:

library:
tag1,paper1
tag2, paper2

Users ought not to be able to lock themselves out of their own libs/groups

user will include some js to go to a library by name/identifier, it will get json, and format it very simply with classes so that user can style as they desire on their page. should be compatible with https://github.com/adsabs/Nasa-ADS-Query-Importer-Widget

use this thread to define them

The trick is to implement this using the proper authentication tokens, presumably via @romanchyla's new API framework.

perhaps has something to do with bigquery not resolving tmps

Need a UI for this. This may not happen for AAS Jan 2014. Then need to also figure a policy forit.

also see if we can bring back autocomplete to the fdropdown, but the libraries should be alphabetic

Compile to js ahead of time by putting into a different file after putting it into a function. The file should only have a one-line js which calls this function. Since its in a template, only that js file should be imported as the last import.

this was alberto's escaping problem

Export as json and csv with tags

The ADSGUT system needs to be fully documented and a comprehensive suite of test cases need to be provided. These are the needed components:

• a document describing the overall architecture of ADSGUT and in particular its main concepts, including the jargon used in the code ("postables," etc.)
• test cases which will make it trivial for a reader to understand what functionality each component is providing
• full description of how the system builds views for two pages: a user's list of libraries and an individual library page

if big query returns an updated bib code, change the library item to accept it

If the note is yours provide a doodad to edit it. This doodad should be
added to postform as well. It would behave similar to the '+' doodad.
This requires changing format_notes_for_item and having notes information coming in.

(a) shows up even if i dont own it (b) shows json error on trying to edit it

Show notes reverse time sorted. Also done in ajax. This then looks like commenting. need to put time/date on, and show which note was edited by user.

When an invite is sent to a user, hook into giovanni's system to send an email

When libraries get large, we will need pagination to not be loading for ever

make tags private by default

We need to review are indexes, especially those for tags to make sure we have enough speed. Also test loading on this, so we dont make bulk loading particularly slow. Investigate if indexing can be turned off in mongodb for loading.

replace group:public by "all ads users"

Once Rahul is back in september, these are the enhancements/modifications to ADSGUT we need to think about:

• create view of libraries in bumblebee
• better view of "libraries" page, adding number of items in each library, real date sort. For more info, see: http://labs.adsabs.harvard.edu/trac/adsabs/ticket/632
• provide API access to webservices
• tighter integration in search interface (e.g. bookmarking of individual records from results list, display of tags in list of results, etc.)
• bug squashing

a test bug

anonymouse got added to ads app twice

I have seen the "Make public" button as well as the list of members disappear from a library's admin page. This happened while the system was quite slow to respond, so it may be difficult to recreate. Do we need to catch cases where a request times out?

Sort items inverse time. Do we do this as ajax or full? For AAS, do ajax as it is faster. Support posting time or alpha based sorting (on bibcode).

Possible need to add sort order to the hash so that it can be used to bookmark.

Add the number of items at the top.

In library page, incorporate solr info on bibcodes, like title, authors and pubdate. Make it look like main search page. Also add a "throw into solr" button.

sees the word anonymouse

Keep a record of this. Its important to do it now as it will affect the mongo class structure which must then be frozen.

for add tag area 9this is not for tag filters), hook it up so that we have an ajax autocompletion on tags.

problem 1 (there are many ambiguities) is that "group" libraries are not disambiguated in the listing. How shall we do this.

Add a line saying no invitations.

Enhance UI to add descriptions when creating new libraries and groups. Also include descriptions in profilepages. This will require enhancing the web services or adding a new one.

On group/lib profile pages you ought to be able to edit the description. We
will not provide this ability on the overall listing page.

Should be in green. Also the same with the notes.

either fix via pagination #22 or add in for long running loads (as user feedback)

Ideally it would be nice for the user to have visual clues about whether he/she authored a tag or not. One suggested solution would be to have all your tags in a separate color.

Actual deletion of tags. Need to decide what happens to group posting and visibility.

• A & A issues
• postables u have access to bug: check access to by being members of groups in libraries. This is important in postform.
• i am pretty sure it is, but audit that all is idempotent

To support additional stuff coming back from items and notes, we might need
to support some additional metadata. This might be actually better done with
an external ajax call, so as to not encounter any leakage.

disable blinker signals on bulk load so that Louise's import speeds up. As a side to this, put loading into a fancybox ajax or a comeback-later button so that
user is not left hanging..

Make sure the loading script is completely idempotent.

By tuesday 6/17 the new database structure should be deployed alongside the current ADSGUT to ensure ample testing of features. Populating this database requires the development of scripts which will upgrade the data structures to the new model, and verifying that all existing functionality works in the new system.

get old library import happen through PORT and an intermediate page where we allow users to select which libraries they want to import

What are the semantics here?

make a public library private. while we can revoke public write privileges, there is no way to "remove" a user/group from a library. This needs that to be done

By the end of the week the coding revamp will be complete. This includes:

• separation of views from webservices
• new model in mongodb to deal with library data in more efficient fashion
• squashing remaining bugs and "todos" as found in current code

user specific stuff shows for anonymouse

That is, remove the checkbox

This may not happen before AAS.

In group interface, a make note public means its public to group. In other contexts it means put to public group. Reflect in UI and audit that it works. Even though no public posting as yet, keep that in? (or remove that ability). We could
alternatively change this to keep note private and remove on saved items