[Rets-dev] Retrieve only changed photos?

[JP Fielding]

as neither option is part of the RETS spec proper, you wouldnt see it in any
rets documentation.  as i stated before, this is something the rets object
stuff does not manage.   but an example would be

NOTE 1: replace MLSNUM with whatever the resource key is for the particular
resource
NOTE 2: you might want to include (PHOTOCOUNT=0+) in the query, although,
someone deleting their all of their photos would be missed.

select=MLSNUM
query=(PHOTODATE=2007-08-12T16:23:00+)

this would give you the mlsnum of listings with photos that have a modified
to at least one of its photos, then iterate over them and pull them

./GetObject?Type=Photo&Resource=PROPERTY&ID=MLSNUM:*

so basically, give the mlsnubers for listings with at least one photo
changed since aug 12 2007... then iterate over these mlsnums and pull them
(unfortunately, all photos per listing as this is the closest granularity
this option offers)

On 8/13/07, Jonathan Heintzeman <heintzeman at gmail.com> wrote:
>
> option 2)
> > query the resource (classes) related to your objects
> >
>
> I fail to see that anywhere in my RETS documentation would you be willing
> to provide an example?
>
>
>
> On 8/13/07, JP Fielding <jp.fielding at threewide.com > wrote:
> >
> > this is something that the rets getobject transaction does not
> > provide.   to get this information, i can suggest 2 paths:
> >
> > option 1)
> > some servers support a MEDIA resource, which can contain various bits of
> > this information (only some vendors support this, and not always the same
> > way)
> >
> > option 2)
> > you can to query the resource (classes) related to your objects, and
> > find the photo count and photo modified dates.   ive seen few servers that
> > dont provide both of these fields.   this would give you an idea of which
> > listings to pull and how many to expect, although i would use the date and
> > then pull all photos for that listing as photo servers and the data arent
> > always kept in sync).  while this is less granular than a date per photo
> > approach, its viable as an implementation across all servers.
> >
> > ../GetObject?Type=Photo&Resource=Property&ID=999999:*&rets-version=rets/1.5
> >
> >
> >
> > hope that helps,
> > jp
> >
> > On 8/13/07, Jonathan Heintzeman <heintzeman at gmail.com> wrote:
> >
> > > I have had no problem retrieving images however I have had trouble
> > > determining which images have changed and how many images a listing has.
> > >
> > > So this gets one photo:
> > >
> > > .../GetObject?Type=Photo&Resource=Property&ID=999999:9&rets-version=rets/1.5
> > >
> > >
> > > Where 9 represents a valid number.
> > >
> > > How do I retrieve only changed photos?
> > >
> > > _______________________________________________
> > > Rets-dev mailing list
> > > Rets-dev at rets.org
> > > http://lists.rets.org/mailman/listinfo/rets-dev
> > >
> > >
> >
>
> _______________________________________________
> Rets-dev mailing list
> Rets-dev at rets.org
> http://lists.rets.org/mailman/listinfo/rets-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rets.org/pipermail/rets-dev/attachments/20070813/7ec62ec0/attachment.html