Changes between Version 1 and Version 2 of GNUGift


Ignore:
Timestamp:
02/21/14 17:42:45 (6 years ago)
Author:
juri
Comment:

pull in content from linuxpmi wiki.

Legend:

Unmodified
Added
Removed
Modified
  • GNUGift

    v1 v2  
     1= New Frontend =
     2
     3= Definition of the New Gift Web Interface =
     4
     5== Authentication and Authorization ==
     6The front-end needs to be plugable into YACMS, by elisa. It needs to perform authentication of a username/password combo, and support authorizing user/group permissions to arbitrary objects.
     7
     8== Opening Page ==
     9After logging into the new interface, the user should first be presented with their visible image sets, and saved sort criteria. Selecting an image set will place them in the browse view for that image set, while selecting a saved sort will place them in the results view for the default image set associated with that sort, displaying results.
     10
     11== Image Sets ==
     12Each images set is a gallery of images to browse. It also has a corresponding GIFT database, and some associated metadata about how it was imported(region selected).
     13
     14== Default Image Sets ==
     15All users have access to an image set named 'Default-origin'. This represent a pristine starting point, and a collection of images every user in the system can view.
     16
     17== Browsing ==
     18Browsing an image set is implemented by performing a random query on GIFT against the image collection, and displaying that result. It should also be possible to specify browse by file name order, or other such name/tag text based sorting. The browse interface should include a 'export as CSV' function, so that this URI may be gotten at with automation scripts.
     19
     20== Searching ==
     21Once a user has selected an image set to browse, the browse interface should include the 'search' interface/functionality of the current frontend.
     22
     23== Results Page ==
     24The result of every search is every image in the database, sorted by how closely they match the images submitted. This should appear very similar to the 'browse' view, including CSV interface. From the results page one should be able to edit the submitted query, rsave the query for future use, return to the browse view of this imageset, or create a new image set from these results.
     25
     26== Image Set Creation ==
     27The user selects a region of the image to 'filter' the view through, when performing a new image recognition pass. This filter is applied to all images in the result set being imported. The user must also select a cutoff point for what is imported into the new image set and what is not. this may be specified either as a count of images from this query starting at the most matched, OR by specifying the minimum match value that an image must match to be included in this image set. There user should hit an 'invert' checkbox to get images that do not match, or are below the value.
     28
     29A new image set created from a search should only be visible to the user that created it.
     30
     31== Tagging ==
     32Users should be able to tag images in result sets belonging to them by specifying a tag, and a cutoff point in a search. Users should also be able to search by tag, instead of image match.
     33
     34= Notes =
     35Comparing to a supplied image is possible, it just needs to be eeked back out of the code.
     36
     37= Previous Frontend =
     38
    139http://megami.faikvm.com/