#1914 Project metadata: Trove categories

v1.0.0
closed
sf-4 (350)
General
nobody
2015-08-20
2011-04-07
No
  • export trove category choices from alexandria; load them into mongo via bootstrap
  • new page under Admin
  • forge-classic hook to save them on the alexandria project record
    • and trigger a solr & gobble update
  • evaluate moving current allura Category values to trove values

Related

Tickets: #2102

Discussion

  • Dave Brondsema

    Dave Brondsema - 2011-04-21
    • Description has changed:

    Diff:

    --- old 
    +++ new 
    @@ -1,5 +1,5 @@
    +* export trove category choices from alexandria; load them into mongo via bootstrap
     * new page under Admin
    -* add all the trove category choices from alexandria
         * like http://screencast.com/t/lAwwlzWUX8qG
         * but use ajax and make it nice!
     * forge-classic hook to save them on the alexandria project record
    
    • size: --> 8
     
  • Jenny Steele - 2011-05-04
    • status: open --> in-progress
    • assigned_to: Jenny Steele
     
  • Jenny Steele - 2011-05-06
    • status: in-progress --> code-review
    • assigned_to: Jenny Steele --> Dave Brondsema
    • milestone: may-12 --> may-05
     
  • Jenny Steele - 2011-05-06

    Changes are on js/1914 on allura and forge-classic. To test, go to the new "Categorization" admin page and add/delete some categories. Make sure the categories get updated in gutenberg too.

    This command needs to be run after push: allurapaste create-trove-categories /var/local/config/production.ini Before that, setup.py will need to run. Does that get run automatically during a push anyway?

     
  • Dave Brondsema

    Dave Brondsema - 2011-05-09

    I have more testing to do, but one thing I noticed is the forge-classic hooks need to do more. Alexandria needs to be updated so that project search and other things have the trove categories. You can look at John's work on [#1998] to see how he did it via the API. Going directly to the DB would be fine too. And then if it's updated in Alexandria, gobble will get the categories and update gutenberge, so the gutenberg update isn't really necessary.

     
  • Dave Brondsema

    Dave Brondsema - 2011-05-09
    • status: code-review --> open
    • assigned_to: Dave Brondsema --> Jenny Steele
     
  • Dave Brondsema

    Dave Brondsema - 2011-05-09

    Also, on /admin/trove/trove_cat_add.php and /admin/trove/trove_cat_edit.php, we should at minimum put a notice saying that changes need to be manually done on the Allura database. (Right now, I don't think its worth updating that code to have it update allura mongo too)

     
  • Dave Brondsema

    Dave Brondsema - 2011-05-09
    • size: 8 --> 4
    • milestone: may-05 --> may-12
     
  • Dave Brondsema

    Dave Brondsema - 2011-05-09

    Made [#2102] to count points of prior work in prior sprint.

    • size: 4 --> 8
     

    Related

    Tickets: #2102

  • Dave Brondsema

    Dave Brondsema - 2011-05-10

    On the UI side, <optgroup> might be nice for the 2-level categories, instead of 2 separate drop-downs. I'm not entirely sure how well that'd work for 3-deep categories though.

     
  • Dave Brondsema

    Dave Brondsema - 2011-05-12
    • size: 8 --> 4
     
  • Jenny Steele - 2011-05-17
    • status: open --> code-review
    • assigned_to: Jenny Steele --> Dave Brondsema
     
  • Jenny Steele - 2011-05-17

    Added the message on sfx js/1914. I also changed the forge-classic code to update in alexandria.

     
  • Dave Brondsema

    Dave Brondsema - 2011-05-19

    I get this when adding trove categories:

      File "/home/dbrondsema/dbrondsema-7024/forge-classic/sfx/sfx_main.py", line 219, in project_updated
       api.update(pylons.c.user, pylons.c.project)
     File "/home/dbrondsema/dbrondsema-7024/forge-classic/sfx/lib/sfx_api.py", line 253, in update
       group_id = r['Project']['id']
    TypeError: string indices must be integers, not str
    

    a few UI suggestions too:

    • change the button from Save to Add
    • move Topic & License to the top of the page, since they're most used
    • indent each subgroup drop-down visually
     
  • Dave Brondsema

    Dave Brondsema - 2011-05-19
    • status: code-review --> in-progress
    • assigned_to: Dave Brondsema --> Jenny Steele
     
  • Jenny Steele - 2011-05-23
    • status: in-progress --> code-review
    • assigned_to: Jenny Steele --> Dave Brondsema
     
  • Dave Brondsema

    Dave Brondsema - 2011-05-27
    • status: code-review --> closed
     

Log in to post a comment.