Bug? Default search view doesn't behave consistently for certain files

[GoogleCodeExporter]

I'm currently working on a tagging control for the UI. Through testing I've 
noticed that some photos are handled differently than others, when:

1) dragged into the app and added to Camlistore (browser gui)
2) the associated permanode is modified (ex: adding or removing a tag attribute)

Environment:
fresh install with only ~15 photos

Expectation:
I noticed that when I add most of my test images into camlistore, or modify an 
attribute of the existing permanodes, the modified item is shuffled to display 
in the top-left corner of the search view.

This works as expected the majority of the time. However, certain images will 
never shuffle to the top-left corner when initially added or later when an 
attribute is modified - the location will always remain the same. Looking in 
more detail at these images that never change positions, they all have a 'time' 
meta field in the referenced camliContent blob's metadata. None of the other 
images (that do change positions) have that field.

It seems like there is some inconsistency in the order in which permanodes are 
displayed. If it is Last Mod Time ordering, then a change of attribute should 
reshuffle any image, regardless of when it was taken. If it is based upon when 
added to camlistore, then a change of attribute shouldn't affect display 
location for any item. But maybe it is a hybrid of when the photo was taken 
combined with LMT if the photo doesn't have a 'time taken' attribute.

Is this behavior expected?

- - - - - - -
{ // this one NEVER updates position in the view

  "meta": {

    "sha1-261842ab64f268d76742a1124a3c1ca798ca49d5": {

      "blobRef": "sha1-261842ab64f268d76742a1124a3c1ca798ca49d5",

      "camliType": "file",

      "size": 888,

      "file": {

        "fileName": "DSC00778.jpg",

        "size": 3342336,

        "mimeType": "image/jpeg",

        "time": "2013-03-30T02:35:23Z"

      },

      "image": {

        "width": 3568,

        "height": 2368

      }

    }

  }

}

- - - - - - - - -

{ // this one ALWAYS updates position in the view

  "meta": {

    "sha1-a57c455d7bb1ce4d7b3dc1ab896b67d394f3b104": {

      "blobRef": "sha1-a57c455d7bb1ce4d7b3dc1ab896b67d394f3b104",

      "camliType": "file",

      "size": 423,

      "file": {

        "fileName": "894937_788759157818410_847788271_o 22.13.31.jpg",

        "size": 357665,

        "mimeType": "image/jpeg"

      },

      "image": {

        "width": 2048,

        "height": 1536

      }

    }

  }

}

Original issue reported on code.google.com by mail...@gmail.com on 19 Sep 2014 at 3:40

Attachments:

• will-NOT-change-position.jpg
• will-change-position.jpg

[GoogleCodeExporter]

Having something like this (below) would definitely help target expected 
behavior. I'll try to look around for the code that handles this and see what 
is currently defaulted.

Sort selector in UI:
https://code.google.com/p/camlistore/issues/detail?id=490

Original comment by mail...@gmail.com on 19 Sep 2014 at 3:54

[GoogleCodeExporter]

The default display order is by content time, which uses the file's EXIF time 
if available. It only falls back to modification time if it can't find any 
other time.

So I think this is is working as intended.  The sorting stuff is still a bit in 
flux, though.

I agree we need to make it easier to change the sorting mode in the UI or 
search.

Original comment by bradfitz on 22 Sep 2014 at 1:34

• Changed state: WorkingAsIntended

[GoogleCodeExporter]

This issue has moved to https://camlistore.org/issue/515

Original comment by bradfitz on 14 Dec 2014 at 11:37

• Added labels: IssueMoved, Restrict-AddIssueComment-Commit