Hi, 
Guest
Pic
Sign In

talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

Ordering Media Snapshot view

KV
Kara Vetter
Fri, Feb 5, 2016 5:23 PM

Hello all!!

So it appears that the Media Snapshot view for multiple images linked to a record are ordered by "Modified Date" rather than by file name.  Is there a known fix or data entry method that will help us overcome this when we want to designate a specific image as the first viewed image in the snapshot?

FYI, we currently title our records using an "_#" system.  E.g. 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view.

It would be nice if there was an option, kind of like a radial dial to select which image is primary once linked to a record but I know that's a complicated thing to create.

Any thoughts are appreciated.

Kara S. Vetter | Registrar
San Diego Museum of Man
1350 El Prado, Balboa Park | San Diego, CA 92101
619-239-2001, ext 44 | kvetter@museumofman.orgmailto:kvetter@museumofman.org

Race: Are We So Different?http://www.museumofman.org/exhibit/race-are-we-so-different
Join us for an eye-opening look at
the reality - and unreality - of race.

Hello all!! So it appears that the Media Snapshot view for multiple images linked to a record are ordered by "Modified Date" rather than by file name. Is there a known fix or data entry method that will help us overcome this when we want to designate a specific image as the first viewed image in the snapshot? FYI, we currently title our records using an "_#" system. E.g. 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view. It would be nice if there was an option, kind of like a radial dial to select which image is primary once linked to a record but I know that's a complicated thing to create. Any thoughts are appreciated. Kara S. Vetter | Registrar San Diego Museum of Man 1350 El Prado, Balboa Park | San Diego, CA 92101 619-239-2001, ext 44 | kvetter@museumofman.org<mailto:kvetter@museumofman.org> Race: Are We So Different?<http://www.museumofman.org/exhibit/race-are-we-so-different> Join us for an eye-opening look at the reality - and unreality - of race.
AR
Aron Roberts
Fri, Feb 5, 2016 5:34 PM

Thanks for this feedback, Kara.

Designating a 'primary' media object has been a long-requested capability;
it's currently captured in:
https://issues.collectionspace.org/browse/CSPACE-3883

On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter kvetter@museumofman.org wrote:

Hello all!!

So it appears that the Media Snapshot view for multiple images linked to a
record are ordered by “Modified Date” rather than by file name.  Is there a
known fix or data entry method that will help us overcome this when we want
to designate a specific image as the first viewed image in the snapshot?

FYI, we currently title our records using an “_#” system.  E.g.
1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view.

It would be nice if there was an option, kind of like a radial dial to
select which image is primary once linked to a record but I know that’s a
complicated thing to create.

Any thoughts are appreciated.

Kara S. Vetter | Registrar

San Diego Museum of Man

1350 El Prado, Balboa Park | San Diego, CA 92101

619-239-2001, ext 44 | kvetter@museumofman.org

Race: Are We So Different?
http://www.museumofman.org/exhibit/race-are-we-so-different

Join us for an eye-opening look at

the reality – and unreality – of race.

Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Thanks for this feedback, Kara. Designating a 'primary' media object has been a long-requested capability; it's currently captured in: https://issues.collectionspace.org/browse/CSPACE-3883 On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.org> wrote: > Hello all!! > > > > So it appears that the Media Snapshot view for multiple images linked to a > record are ordered by “Modified Date” rather than by file name. Is there a > known fix or data entry method that will help us overcome this when we want > to designate a specific image as the first viewed image in the snapshot? > > > > FYI, we currently title our records using an “_#” system. E.g. > 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view. > > > > It would be nice if there was an option, kind of like a radial dial to > select which image is primary once linked to a record but I know that’s a > complicated thing to create. > > > > Any thoughts are appreciated. > > > > Kara S. Vetter | Registrar > > San Diego Museum of Man > > 1350 El Prado, Balboa Park | San Diego, CA 92101 > > 619-239-2001, ext 44 | kvetter@museumofman.org > > > > *Race: Are We So Different?* > <http://www.museumofman.org/exhibit/race-are-we-so-different> > > Join us for an eye-opening look at > > the reality – and unreality – of race. > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >
SS
Susan STONE
Fri, Feb 5, 2016 6:02 PM

Kara,

As Aron mentions, I also know of several collections who want this
functionality--looks like I reported it a long time ago. These collections
have added a primary image flag in their custom fields, but it is just
informative--it doesn't make that image appear first. But I think you can
modify the record of the one you want to appear first--even if it is a
bogus change.

Please vote for the old issue Aron points out.

Susan

On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter kvetter@museumofman.org wrote:

Hello all!!

So it appears that the Media Snapshot view for multiple images linked to a
record are ordered by “Modified Date” rather than by file name.  Is there a
known fix or data entry method that will help us overcome this when we want
to designate a specific image as the first viewed image in the snapshot?

FYI, we currently title our records using an “_#” system.  E.g.
1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view.

It would be nice if there was an option, kind of like a radial dial to
select which image is primary once linked to a record but I know that’s a
complicated thing to create.

Any thoughts are appreciated.

Kara S. Vetter | Registrar

San Diego Museum of Man

1350 El Prado, Balboa Park | San Diego, CA 92101

619-239-2001, ext 44 | kvetter@museumofman.org

Race: Are We So Different?
http://www.museumofman.org/exhibit/race-are-we-so-different

Join us for an eye-opening look at

the reality – and unreality – of race.

Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Kara, As Aron mentions, I also know of several collections who want this functionality--looks like I reported it a long time ago. These collections have added a primary image flag in their custom fields, but it is just informative--it doesn't make that image appear first. But I think you can modify the record of the one you want to appear first--even if it is a bogus change. Please vote for the old issue Aron points out. Susan On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.org> wrote: > Hello all!! > > > > So it appears that the Media Snapshot view for multiple images linked to a > record are ordered by “Modified Date” rather than by file name. Is there a > known fix or data entry method that will help us overcome this when we want > to designate a specific image as the first viewed image in the snapshot? > > > > FYI, we currently title our records using an “_#” system. E.g. > 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view. > > > > It would be nice if there was an option, kind of like a radial dial to > select which image is primary once linked to a record but I know that’s a > complicated thing to create. > > > > Any thoughts are appreciated. > > > > Kara S. Vetter | Registrar > > San Diego Museum of Man > > 1350 El Prado, Balboa Park | San Diego, CA 92101 > > 619-239-2001, ext 44 | kvetter@museumofman.org > > > > *Race: Are We So Different?* > <http://www.museumofman.org/exhibit/race-are-we-so-different> > > Join us for an eye-opening look at > > the reality – and unreality – of race. > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >
JB
John B Lowe
Fri, Feb 5, 2016 6:25 PM

Kara,

In fact, there are two different solutions to this problem in use in the
UCB deployments:

  • A checkbox on Media records that sets a image as "primary". This does not
    specify an order for other images associated with an objects (This is
    deployed for PAHMA).

  • A "page number" field on Media records that does what you seem to need:
    allows the user to specify an ordering of images. (This is deployed for
    BAMPFA.)

We have a request for one of these two functionalities from the UC
Botanical Garden, and we in the throes of deciding which of the two
functionalities will best meet their needs.

The current request is:

https://issues.collectionspace.org/browse/UCBG-431

I'll try to update that with the related issues for completeness.

The point is, the code has been written to do this, and your deployment
could be customized to include it...

Regards,

John

On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE sstone@berkeley.edu wrote:

Kara,

As Aron mentions, I also know of several collections who want this
functionality--looks like I reported it a long time ago. These collections
have added a primary image flag in their custom fields, but it is just
informative--it doesn't make that image appear first. But I think you can
modify the record of the one you want to appear first--even if it is a
bogus change.

Please vote for the old issue Aron points out.

Susan

On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter kvetter@museumofman.org
wrote:

Hello all!!

So it appears that the Media Snapshot view for multiple images linked to
a record are ordered by “Modified Date” rather than by file name.  Is there
a known fix or data entry method that will help us overcome this when we
want to designate a specific image as the first viewed image in the
snapshot?

FYI, we currently title our records using an “_#” system.  E.g.
1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view.

It would be nice if there was an option, kind of like a radial dial to
select which image is primary once linked to a record but I know that’s a
complicated thing to create.

Any thoughts are appreciated.

Kara S. Vetter | Registrar

San Diego Museum of Man

1350 El Prado, Balboa Park | San Diego, CA 92101

619-239-2001, ext 44 | kvetter@museumofman.org

Race: Are We So Different?
http://www.museumofman.org/exhibit/race-are-we-so-different

Join us for an eye-opening look at

the reality – and unreality – of race.

Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Kara, In fact, there are two different solutions to this problem in use in the UCB deployments: * A checkbox on Media records that sets a image as "primary". This does not specify an order for other images associated with an objects (This is deployed for PAHMA). * A "page number" field on Media records that does what you seem to need: allows the user to specify an ordering of images. (This is deployed for BAMPFA.) We have a request for one of these two functionalities from the UC Botanical Garden, and we in the throes of deciding which of the two functionalities will best meet their needs. The current request is: https://issues.collectionspace.org/browse/UCBG-431 I'll try to update that with the related issues for completeness. The point is, the code has been written to do this, and your deployment could be customized to include it... Regards, John On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE <sstone@berkeley.edu> wrote: > Kara, > > As Aron mentions, I also know of several collections who want this > functionality--looks like I reported it a long time ago. These collections > have added a primary image flag in their custom fields, but it is just > informative--it doesn't make that image appear first. But I think you can > modify the record of the one you want to appear first--even if it is a > bogus change. > > Please vote for the old issue Aron points out. > > Susan > > On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.org> > wrote: > >> Hello all!! >> >> >> >> So it appears that the Media Snapshot view for multiple images linked to >> a record are ordered by “Modified Date” rather than by file name. Is there >> a known fix or data entry method that will help us overcome this when we >> want to designate a specific image as the first viewed image in the >> snapshot? >> >> >> >> FYI, we currently title our records using an “_#” system. E.g. >> 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view. >> >> >> >> It would be nice if there was an option, kind of like a radial dial to >> select which image is primary once linked to a record but I know that’s a >> complicated thing to create. >> >> >> >> Any thoughts are appreciated. >> >> >> >> Kara S. Vetter | Registrar >> >> San Diego Museum of Man >> >> 1350 El Prado, Balboa Park | San Diego, CA 92101 >> >> 619-239-2001, ext 44 | kvetter@museumofman.org >> >> >> >> *Race: Are We So Different?* >> <http://www.museumofman.org/exhibit/race-are-we-so-different> >> >> Join us for an eye-opening look at >> >> the reality – and unreality – of race. >> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >
RM
Richard Millet
Fri, Feb 5, 2016 6:36 PM

Thanks John.  Do you think this is something that could/should be contributed to the core code?  If so, Megan and the Functional Working group could approve and review the idea and then a pull request could be made to the core repository.

From: Talk talk-bounces@lists.collectionspace.org on behalf of John B Lowe jblowe@berkeley.edu
Sent: Friday, February 05, 2016 10:25 AM
To: Kara Vetter
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Ordering Media Snapshot view

Kara,

In fact, there are two different solutions to this problem in use in the UCB deployments:

  • A checkbox on Media records that sets a image as "primary". This does not specify an order for other images associated with an objects (This is deployed for PAHMA).

  • A "page number" field on Media records that does what you seem to need: allows the user to specify an ordering of images. (This is deployed for BAMPFA.)

We have a request for one of these two functionalities from the UC Botanical Garden, and we in the throes of deciding which of the two functionalities will best meet their needs.

The current request is:

https://issues.collectionspace.org/browse/UCBG-431

I'll try to update that with the related issues for completeness.

The point is, the code has been written to do this, and your deployment could be customized to include it...

Regards,

John

On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE <sstone@berkeley.edumailto:sstone@berkeley.edu> wrote:
Kara,

As Aron mentions, I also know of several collections who want this functionality--looks like I reported it a long time ago. These collections have added a primary image flag in their custom fields, but it is just informative--it doesn't make that image appear first. But I think you can modify the record of the one you want to appear first--even if it is a bogus change.

Please vote for the old issue Aron points out.

Susan

On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.orgmailto:kvetter@museumofman.org> wrote:
Hello all!!

So it appears that the Media Snapshot view for multiple images linked to a record are ordered by "Modified Date" rather than by file name.  Is there a known fix or data entry method that will help us overcome this when we want to designate a specific image as the first viewed image in the snapshot?

FYI, we currently title our records using an "_#" system.  E.g. 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view.

It would be nice if there was an option, kind of like a radial dial to select which image is primary once linked to a record but I know that's a complicated thing to create.

Any thoughts are appreciated.

Kara S. Vetter | Registrar
San Diego Museum of Man
1350 El Prado, Balboa Park | San Diego, CA 92101
619-239-2001, ext 44tel:619-239-2001%2C%20ext%2044 | kvetter@museumofman.orgmailto:kvetter@museumofman.org

Race: Are We So Different?http://www.museumofman.org/exhibit/race-are-we-so-different
Join us for an eye-opening look at
the reality - and unreality - of race.

Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Thanks John. Do you think this is something that could/should be contributed to the core code? If so, Megan and the Functional Working group could approve and review the idea and then a pull request could be made to the core repository. ________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of John B Lowe <jblowe@berkeley.edu> Sent: Friday, February 05, 2016 10:25 AM To: Kara Vetter Cc: talk@lists.collectionspace.org Subject: Re: [Talk] Ordering Media Snapshot view Kara, In fact, there are two different solutions to this problem in use in the UCB deployments: * A checkbox on Media records that sets a image as "primary". This does not specify an order for other images associated with an objects (This is deployed for PAHMA). * A "page number" field on Media records that does what you seem to need: allows the user to specify an ordering of images. (This is deployed for BAMPFA.) We have a request for one of these two functionalities from the UC Botanical Garden, and we in the throes of deciding which of the two functionalities will best meet their needs. The current request is: https://issues.collectionspace.org/browse/UCBG-431 I'll try to update that with the related issues for completeness. The point is, the code has been written to do this, and your deployment could be customized to include it... Regards, John On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE <sstone@berkeley.edu<mailto:sstone@berkeley.edu>> wrote: Kara, As Aron mentions, I also know of several collections who want this functionality--looks like I reported it a long time ago. These collections have added a primary image flag in their custom fields, but it is just informative--it doesn't make that image appear first. But I think you can modify the record of the one you want to appear first--even if it is a bogus change. Please vote for the old issue Aron points out. Susan On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.org<mailto:kvetter@museumofman.org>> wrote: Hello all!! So it appears that the Media Snapshot view for multiple images linked to a record are ordered by "Modified Date" rather than by file name. Is there a known fix or data entry method that will help us overcome this when we want to designate a specific image as the first viewed image in the snapshot? FYI, we currently title our records using an "_#" system. E.g. 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view. It would be nice if there was an option, kind of like a radial dial to select which image is primary once linked to a record but I know that's a complicated thing to create. Any thoughts are appreciated. Kara S. Vetter | Registrar San Diego Museum of Man 1350 El Prado, Balboa Park | San Diego, CA 92101 619-239-2001, ext 44<tel:619-239-2001%2C%20ext%2044> | kvetter@museumofman.org<mailto:kvetter@museumofman.org> Race: Are We So Different?<http://www.museumofman.org/exhibit/race-are-we-so-different> Join us for an eye-opening look at the reality - and unreality - of race. _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
RL
Ray Lee
Fri, Feb 5, 2016 7:19 PM

As a default I think it should sort by filename. I suspect that would
satisfy most people. This would be trivial if the filename were returned in
media list results -- but the filename is on the blob record, not the media
record. It would be nice if the services layer automatically denormalized
the blob filename into the media record (e.g. via event handler). Even if
you don't use the filename to sort, it's often useful to display in search
results and the sidebar.

The stuff John described is what we could do in the short term, but it's
pretty clunky. First of all, the data model is broken. What if a media
record is related to multiple objects, and it should show up first in one,
but not the other? The ordering field properly belongs on the relation
record. If we had that field, we could implement drag-and-drop reordering
somewhere; possibly, in the media snapshot browser itself.

Ray

On Fri, Feb 5, 2016 at 10:36 AM, Richard Millet richard.millet@lyrasis.org
wrote:

Thanks John.  Do you think this is something that could/should be
contributed to the core code?  If so, Megan and the Functional Working
group could approve and review the idea and then a pull request could be
made to the core repository.

From: Talk talk-bounces@lists.collectionspace.org on behalf of John B
Lowe jblowe@berkeley.edu
Sent: Friday, February 05, 2016 10:25 AM
To: Kara Vetter
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Ordering Media Snapshot view

Kara,

In fact, there are two different solutions to this problem in use in the
UCB deployments:

  • A checkbox on Media records that sets a image as "primary". This does
    not specify an order for other images associated with an objects (This is
    deployed for PAHMA).

  • A "page number" field on Media records that does what you seem to need:
    allows the user to specify an ordering of images. (This is deployed for
    BAMPFA.)

We have a request for one of these two functionalities from the UC
Botanical Garden, and we in the throes of deciding which of the two
functionalities will best meet their needs.

The current request is:

https://issues.collectionspace.org/browse/UCBG-431

I'll try to update that with the related issues for completeness.

The point is, the code has been written to do this, and your deployment
could be customized to include it...

Regards,

John

On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE sstone@berkeley.edu wrote:

Kara,

As Aron mentions, I also know of several collections who want this
functionality--looks like I reported it a long time ago. These collections
have added a primary image flag in their custom fields, but it is just
informative--it doesn't make that image appear first. But I think you can
modify the record of the one you want to appear first--even if it is a
bogus change.

Please vote for the old issue Aron points out.

Susan

On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter kvetter@museumofman.org
wrote:

Hello all!!

So it appears that the Media Snapshot view for multiple images linked to
a record are ordered by “Modified Date” rather than by file name.  Is there
a known fix or data entry method that will help us overcome this when we
want to designate a specific image as the first viewed image in the
snapshot?

FYI, we currently title our records using an “_#” system.  E.g.
1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view.

It would be nice if there was an option, kind of like a radial dial to
select which image is primary once linked to a record but I know that’s a
complicated thing to create.

Any thoughts are appreciated.

Kara S. Vetter | Registrar

San Diego Museum of Man

1350 El Prado, Balboa Park | San Diego, CA 92101

619-239-2001, ext 44 | kvetter@museumofman.org

Race: Are We So Different?
http://www.museumofman.org/exhibit/race-are-we-so-different

Join us for an eye-opening look at

the reality – and unreality – of race.

Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

As a default I think it should sort by filename. I suspect that would satisfy most people. This would be trivial if the filename were returned in media list results -- but the filename is on the blob record, not the media record. It would be nice if the services layer automatically denormalized the blob filename into the media record (e.g. via event handler). Even if you don't use the filename to sort, it's often useful to display in search results and the sidebar. The stuff John described is what we could do in the short term, but it's pretty clunky. First of all, the data model is broken. What if a media record is related to multiple objects, and it should show up first in one, but not the other? The ordering field properly belongs on the relation record. If we had that field, we could implement drag-and-drop reordering somewhere; possibly, in the media snapshot browser itself. Ray On Fri, Feb 5, 2016 at 10:36 AM, Richard Millet <richard.millet@lyrasis.org> wrote: > Thanks John. Do you think this is something that could/should be > contributed to the core code? If so, Megan and the Functional Working > group could approve and review the idea and then a pull request could be > made to the core repository. > > > ------------------------------ > *From:* Talk <talk-bounces@lists.collectionspace.org> on behalf of John B > Lowe <jblowe@berkeley.edu> > *Sent:* Friday, February 05, 2016 10:25 AM > *To:* Kara Vetter > *Cc:* talk@lists.collectionspace.org > *Subject:* Re: [Talk] Ordering Media Snapshot view > > Kara, > > In fact, there are two different solutions to this problem in use in the > UCB deployments: > > * A checkbox on Media records that sets a image as "primary". This does > not specify an order for other images associated with an objects (This is > deployed for PAHMA). > > * A "page number" field on Media records that does what you seem to need: > allows the user to specify an ordering of images. (This is deployed for > BAMPFA.) > > We have a request for one of these two functionalities from the UC > Botanical Garden, and we in the throes of deciding which of the two > functionalities will best meet their needs. > > The current request is: > > https://issues.collectionspace.org/browse/UCBG-431 > > I'll try to update that with the related issues for completeness. > > The point is, the code has been written to do this, and your deployment > could be customized to include it... > > Regards, > > John > > On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE <sstone@berkeley.edu> wrote: > >> Kara, >> >> As Aron mentions, I also know of several collections who want this >> functionality--looks like I reported it a long time ago. These collections >> have added a primary image flag in their custom fields, but it is just >> informative--it doesn't make that image appear first. But I think you can >> modify the record of the one you want to appear first--even if it is a >> bogus change. >> >> Please vote for the old issue Aron points out. >> >> Susan >> >> On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.org> >> wrote: >> >>> Hello all!! >>> >>> >>> >>> So it appears that the Media Snapshot view for multiple images linked to >>> a record are ordered by “Modified Date” rather than by file name. Is there >>> a known fix or data entry method that will help us overcome this when we >>> want to designate a specific image as the first viewed image in the >>> snapshot? >>> >>> >>> >>> FYI, we currently title our records using an “_#” system. E.g. >>> 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view. >>> >>> >>> >>> It would be nice if there was an option, kind of like a radial dial to >>> select which image is primary once linked to a record but I know that’s a >>> complicated thing to create. >>> >>> >>> >>> Any thoughts are appreciated. >>> >>> >>> >>> Kara S. Vetter | Registrar >>> >>> San Diego Museum of Man >>> >>> 1350 El Prado, Balboa Park | San Diego, CA 92101 >>> >>> 619-239-2001, ext 44 | kvetter@museumofman.org >>> >>> >>> >>> *Race: Are We So Different?* >>> <http://www.museumofman.org/exhibit/race-are-we-so-different> >>> >>> Join us for an eye-opening look at >>> >>> the reality – and unreality – of race. >>> >>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >>> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >
RL
Ray Lee
Fri, Feb 5, 2016 7:31 PM

I forgot to finish my thought about the clunkiness of our current approach:
with the ordering field on the media record, it means that to do a
reordering, you have to edit every media record individually, and change
the number to the correct new number. It's pretty painful. That's why a
drag-and-drop interface would be nice.

Ray

On Fri, Feb 5, 2016 at 11:19 AM, Ray Lee rhlee@berkeley.edu wrote:

As a default I think it should sort by filename. I suspect that would
satisfy most people. This would be trivial if the filename were returned in
media list results -- but the filename is on the blob record, not the media
record. It would be nice if the services layer automatically denormalized
the blob filename into the media record (e.g. via event handler). Even if
you don't use the filename to sort, it's often useful to display in search
results and the sidebar.

The stuff John described is what we could do in the short term, but it's
pretty clunky. First of all, the data model is broken. What if a media
record is related to multiple objects, and it should show up first in one,
but not the other? The ordering field properly belongs on the relation
record. If we had that field, we could implement drag-and-drop reordering
somewhere; possibly, in the media snapshot browser itself.

Ray

On Fri, Feb 5, 2016 at 10:36 AM, Richard Millet <
richard.millet@lyrasis.org> wrote:

Thanks John.  Do you think this is something that could/should be
contributed to the core code?  If so, Megan and the Functional Working
group could approve and review the idea and then a pull request could be
made to the core repository.

From: Talk talk-bounces@lists.collectionspace.org on behalf of John
B Lowe jblowe@berkeley.edu
Sent: Friday, February 05, 2016 10:25 AM
To: Kara Vetter
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Ordering Media Snapshot view

Kara,

In fact, there are two different solutions to this problem in use in the
UCB deployments:

  • A checkbox on Media records that sets a image as "primary". This does
    not specify an order for other images associated with an objects (This is
    deployed for PAHMA).

  • A "page number" field on Media records that does what you seem to need:
    allows the user to specify an ordering of images. (This is deployed for
    BAMPFA.)

We have a request for one of these two functionalities from the UC
Botanical Garden, and we in the throes of deciding which of the two
functionalities will best meet their needs.

The current request is:

https://issues.collectionspace.org/browse/UCBG-431

I'll try to update that with the related issues for completeness.

The point is, the code has been written to do this, and your deployment
could be customized to include it...

Regards,

John

On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE sstone@berkeley.edu wrote:

Kara,

As Aron mentions, I also know of several collections who want this
functionality--looks like I reported it a long time ago. These collections
have added a primary image flag in their custom fields, but it is just
informative--it doesn't make that image appear first. But I think you can
modify the record of the one you want to appear first--even if it is a
bogus change.

Please vote for the old issue Aron points out.

Susan

On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter kvetter@museumofman.org
wrote:

Hello all!!

So it appears that the Media Snapshot view for multiple images linked
to a record are ordered by “Modified Date” rather than by file name.  Is
there a known fix or data entry method that will help us overcome this when
we want to designate a specific image as the first viewed image in the
snapshot?

FYI, we currently title our records using an “_#” system.  E.g.
1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view.

It would be nice if there was an option, kind of like a radial dial to
select which image is primary once linked to a record but I know that’s a
complicated thing to create.

Any thoughts are appreciated.

Kara S. Vetter | Registrar

San Diego Museum of Man

1350 El Prado, Balboa Park | San Diego, CA 92101

619-239-2001, ext 44 | kvetter@museumofman.org

Race: Are We So Different?
http://www.museumofman.org/exhibit/race-are-we-so-different

Join us for an eye-opening look at

the reality – and unreality – of race.

Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

I forgot to finish my thought about the clunkiness of our current approach: with the ordering field on the media record, it means that to do a reordering, you have to edit every media record individually, and change the number to the correct new number. It's pretty painful. That's why a drag-and-drop interface would be nice. Ray On Fri, Feb 5, 2016 at 11:19 AM, Ray Lee <rhlee@berkeley.edu> wrote: > As a default I think it should sort by filename. I suspect that would > satisfy most people. This would be trivial if the filename were returned in > media list results -- but the filename is on the blob record, not the media > record. It would be nice if the services layer automatically denormalized > the blob filename into the media record (e.g. via event handler). Even if > you don't use the filename to sort, it's often useful to display in search > results and the sidebar. > > The stuff John described is what we could do in the short term, but it's > pretty clunky. First of all, the data model is broken. What if a media > record is related to multiple objects, and it should show up first in one, > but not the other? The ordering field properly belongs on the relation > record. If we had that field, we could implement drag-and-drop reordering > somewhere; possibly, in the media snapshot browser itself. > > Ray > > > On Fri, Feb 5, 2016 at 10:36 AM, Richard Millet < > richard.millet@lyrasis.org> wrote: > >> Thanks John. Do you think this is something that could/should be >> contributed to the core code? If so, Megan and the Functional Working >> group could approve and review the idea and then a pull request could be >> made to the core repository. >> >> >> ------------------------------ >> *From:* Talk <talk-bounces@lists.collectionspace.org> on behalf of John >> B Lowe <jblowe@berkeley.edu> >> *Sent:* Friday, February 05, 2016 10:25 AM >> *To:* Kara Vetter >> *Cc:* talk@lists.collectionspace.org >> *Subject:* Re: [Talk] Ordering Media Snapshot view >> >> Kara, >> >> In fact, there are two different solutions to this problem in use in the >> UCB deployments: >> >> * A checkbox on Media records that sets a image as "primary". This does >> not specify an order for other images associated with an objects (This is >> deployed for PAHMA). >> >> * A "page number" field on Media records that does what you seem to need: >> allows the user to specify an ordering of images. (This is deployed for >> BAMPFA.) >> >> We have a request for one of these two functionalities from the UC >> Botanical Garden, and we in the throes of deciding which of the two >> functionalities will best meet their needs. >> >> The current request is: >> >> https://issues.collectionspace.org/browse/UCBG-431 >> >> I'll try to update that with the related issues for completeness. >> >> The point is, the code has been written to do this, and your deployment >> could be customized to include it... >> >> Regards, >> >> John >> >> On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE <sstone@berkeley.edu> wrote: >> >>> Kara, >>> >>> As Aron mentions, I also know of several collections who want this >>> functionality--looks like I reported it a long time ago. These collections >>> have added a primary image flag in their custom fields, but it is just >>> informative--it doesn't make that image appear first. But I think you can >>> modify the record of the one you want to appear first--even if it is a >>> bogus change. >>> >>> Please vote for the old issue Aron points out. >>> >>> Susan >>> >>> On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.org> >>> wrote: >>> >>>> Hello all!! >>>> >>>> >>>> >>>> So it appears that the Media Snapshot view for multiple images linked >>>> to a record are ordered by “Modified Date” rather than by file name. Is >>>> there a known fix or data entry method that will help us overcome this when >>>> we want to designate a specific image as the first viewed image in the >>>> snapshot? >>>> >>>> >>>> >>>> FYI, we currently title our records using an “_#” system. E.g. >>>> 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view. >>>> >>>> >>>> >>>> It would be nice if there was an option, kind of like a radial dial to >>>> select which image is primary once linked to a record but I know that’s a >>>> complicated thing to create. >>>> >>>> >>>> >>>> Any thoughts are appreciated. >>>> >>>> >>>> >>>> Kara S. Vetter | Registrar >>>> >>>> San Diego Museum of Man >>>> >>>> 1350 El Prado, Balboa Park | San Diego, CA 92101 >>>> >>>> 619-239-2001, ext 44 | kvetter@museumofman.org >>>> >>>> >>>> >>>> *Race: Are We So Different?* >>>> <http://www.museumofman.org/exhibit/race-are-we-so-different> >>>> >>>> Join us for an eye-opening look at >>>> >>>> the reality – and unreality – of race. >>>> >>>> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >>>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >>> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> >
JB
John B Lowe
Fri, Feb 5, 2016 7:53 PM

Richard,

Yes, I think some implementation of this functionality could and should be
contributed to the core -- every UCB deployment has had to do something
about this situation, so it is probably ubiquitous. As Ray notes, there is
currently some clunkiness and some other bits might even be a bit broken,
so we'd want to understand what a robust solution looks like in some
detail. Not huge (says he who would probably have little to do with actual
implementation! ;-) but not small either...

On Fri, Feb 5, 2016 at 11:31 AM, Ray Lee rhlee@berkeley.edu wrote:

I forgot to finish my thought about the clunkiness of our current
approach: with the ordering field on the media record, it means that to do
a reordering, you have to edit every media record individually, and change
the number to the correct new number. It's pretty painful. That's why a
drag-and-drop interface would be nice.

Ray

On Fri, Feb 5, 2016 at 11:19 AM, Ray Lee rhlee@berkeley.edu wrote:

As a default I think it should sort by filename. I suspect that would
satisfy most people. This would be trivial if the filename were returned in
media list results -- but the filename is on the blob record, not the media
record. It would be nice if the services layer automatically denormalized
the blob filename into the media record (e.g. via event handler). Even if
you don't use the filename to sort, it's often useful to display in search
results and the sidebar.

The stuff John described is what we could do in the short term, but it's
pretty clunky. First of all, the data model is broken. What if a media
record is related to multiple objects, and it should show up first in one,
but not the other? The ordering field properly belongs on the relation
record. If we had that field, we could implement drag-and-drop reordering
somewhere; possibly, in the media snapshot browser itself.

Ray

On Fri, Feb 5, 2016 at 10:36 AM, Richard Millet <
richard.millet@lyrasis.org> wrote:

Thanks John.  Do you think this is something that could/should be
contributed to the core code?  If so, Megan and the Functional Working
group could approve and review the idea and then a pull request could be
made to the core repository.

From: Talk talk-bounces@lists.collectionspace.org on behalf of John
B Lowe jblowe@berkeley.edu
Sent: Friday, February 05, 2016 10:25 AM
To: Kara Vetter
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Ordering Media Snapshot view

Kara,

In fact, there are two different solutions to this problem in use in the
UCB deployments:

  • A checkbox on Media records that sets a image as "primary". This does
    not specify an order for other images associated with an objects (This is
    deployed for PAHMA).

  • A "page number" field on Media records that does what you seem to
    need: allows the user to specify an ordering of images. (This is deployed
    for BAMPFA.)

We have a request for one of these two functionalities from the UC
Botanical Garden, and we in the throes of deciding which of the two
functionalities will best meet their needs.

The current request is:

https://issues.collectionspace.org/browse/UCBG-431

I'll try to update that with the related issues for completeness.

The point is, the code has been written to do this, and your deployment
could be customized to include it...

Regards,

John

On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE sstone@berkeley.edu
wrote:

Kara,

As Aron mentions, I also know of several collections who want this
functionality--looks like I reported it a long time ago. These collections
have added a primary image flag in their custom fields, but it is just
informative--it doesn't make that image appear first. But I think you can
modify the record of the one you want to appear first--even if it is a
bogus change.

Please vote for the old issue Aron points out.

Susan

On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter kvetter@museumofman.org
wrote:

Hello all!!

So it appears that the Media Snapshot view for multiple images linked
to a record are ordered by “Modified Date” rather than by file name.  Is
there a known fix or data entry method that will help us overcome this when
we want to designate a specific image as the first viewed image in the
snapshot?

FYI, we currently title our records using an “_#” system.  E.g.
1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view.

It would be nice if there was an option, kind of like a radial dial to
select which image is primary once linked to a record but I know that’s a
complicated thing to create.

Any thoughts are appreciated.

Kara S. Vetter | Registrar

San Diego Museum of Man

1350 El Prado, Balboa Park | San Diego, CA 92101

619-239-2001, ext 44 | kvetter@museumofman.org

Race: Are We So Different?
http://www.museumofman.org/exhibit/race-are-we-so-different

Join us for an eye-opening look at

the reality – and unreality – of race.

Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Richard, Yes, I think some implementation of this functionality could and should be contributed to the core -- every UCB deployment has had to do something about this situation, so it is probably ubiquitous. As Ray notes, there is currently some clunkiness and some other bits might even be a bit broken, so we'd want to understand what a robust solution looks like in some detail. Not huge (says he who would probably have little to do with actual implementation! ;-) but not small either... On Fri, Feb 5, 2016 at 11:31 AM, Ray Lee <rhlee@berkeley.edu> wrote: > I forgot to finish my thought about the clunkiness of our current > approach: with the ordering field on the media record, it means that to do > a reordering, you have to edit every media record individually, and change > the number to the correct new number. It's pretty painful. That's why a > drag-and-drop interface would be nice. > > Ray > > On Fri, Feb 5, 2016 at 11:19 AM, Ray Lee <rhlee@berkeley.edu> wrote: > >> As a default I think it should sort by filename. I suspect that would >> satisfy most people. This would be trivial if the filename were returned in >> media list results -- but the filename is on the blob record, not the media >> record. It would be nice if the services layer automatically denormalized >> the blob filename into the media record (e.g. via event handler). Even if >> you don't use the filename to sort, it's often useful to display in search >> results and the sidebar. >> >> The stuff John described is what we could do in the short term, but it's >> pretty clunky. First of all, the data model is broken. What if a media >> record is related to multiple objects, and it should show up first in one, >> but not the other? The ordering field properly belongs on the relation >> record. If we had that field, we could implement drag-and-drop reordering >> somewhere; possibly, in the media snapshot browser itself. >> >> Ray >> >> >> On Fri, Feb 5, 2016 at 10:36 AM, Richard Millet < >> richard.millet@lyrasis.org> wrote: >> >>> Thanks John. Do you think this is something that could/should be >>> contributed to the core code? If so, Megan and the Functional Working >>> group could approve and review the idea and then a pull request could be >>> made to the core repository. >>> >>> >>> ------------------------------ >>> *From:* Talk <talk-bounces@lists.collectionspace.org> on behalf of John >>> B Lowe <jblowe@berkeley.edu> >>> *Sent:* Friday, February 05, 2016 10:25 AM >>> *To:* Kara Vetter >>> *Cc:* talk@lists.collectionspace.org >>> *Subject:* Re: [Talk] Ordering Media Snapshot view >>> >>> Kara, >>> >>> In fact, there are two different solutions to this problem in use in the >>> UCB deployments: >>> >>> * A checkbox on Media records that sets a image as "primary". This does >>> not specify an order for other images associated with an objects (This is >>> deployed for PAHMA). >>> >>> * A "page number" field on Media records that does what you seem to >>> need: allows the user to specify an ordering of images. (This is deployed >>> for BAMPFA.) >>> >>> We have a request for one of these two functionalities from the UC >>> Botanical Garden, and we in the throes of deciding which of the two >>> functionalities will best meet their needs. >>> >>> The current request is: >>> >>> https://issues.collectionspace.org/browse/UCBG-431 >>> >>> I'll try to update that with the related issues for completeness. >>> >>> The point is, the code has been written to do this, and your deployment >>> could be customized to include it... >>> >>> Regards, >>> >>> John >>> >>> On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE <sstone@berkeley.edu> >>> wrote: >>> >>>> Kara, >>>> >>>> As Aron mentions, I also know of several collections who want this >>>> functionality--looks like I reported it a long time ago. These collections >>>> have added a primary image flag in their custom fields, but it is just >>>> informative--it doesn't make that image appear first. But I think you can >>>> modify the record of the one you want to appear first--even if it is a >>>> bogus change. >>>> >>>> Please vote for the old issue Aron points out. >>>> >>>> Susan >>>> >>>> On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.org> >>>> wrote: >>>> >>>>> Hello all!! >>>>> >>>>> >>>>> >>>>> So it appears that the Media Snapshot view for multiple images linked >>>>> to a record are ordered by “Modified Date” rather than by file name. Is >>>>> there a known fix or data entry method that will help us overcome this when >>>>> we want to designate a specific image as the first viewed image in the >>>>> snapshot? >>>>> >>>>> >>>>> >>>>> FYI, we currently title our records using an “_#” system. E.g. >>>>> 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view. >>>>> >>>>> >>>>> >>>>> It would be nice if there was an option, kind of like a radial dial to >>>>> select which image is primary once linked to a record but I know that’s a >>>>> complicated thing to create. >>>>> >>>>> >>>>> >>>>> Any thoughts are appreciated. >>>>> >>>>> >>>>> >>>>> Kara S. Vetter | Registrar >>>>> >>>>> San Diego Museum of Man >>>>> >>>>> 1350 El Prado, Balboa Park | San Diego, CA 92101 >>>>> >>>>> 619-239-2001, ext 44 | kvetter@museumofman.org >>>>> >>>>> >>>>> >>>>> *Race: Are We So Different?* >>>>> <http://www.museumofman.org/exhibit/race-are-we-so-different> >>>>> >>>>> Join us for an eye-opening look at >>>>> >>>>> the reality – and unreality – of race. >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Talk mailing list >>>>> Talk@lists.collectionspace.org >>>>> >>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >>>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >>> >> >
MF
Megan Forbes
Fri, Feb 5, 2016 8:19 PM

Thanks for bringing up the relation record, Ray. It was present in our earliest wireframes, and would also be useful for typing relationships.

Megan Forbes
CollectionSpace Program Manager
megan.forbes@lyrasis.org
917.267.9676 Cell
meganbforbes Skype

From: Talk talk-bounces@lists.collectionspace.org on behalf of Ray Lee rhlee@berkeley.edu
Sent: Friday, February 5, 2016 2:19 PM
To: Richard Millet
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Ordering Media Snapshot view

As a default I think it should sort by filename. I suspect that would satisfy most people. This would be trivial if the filename were returned in media list results -- but the filename is on the blob record, not the media record. It would be nice if the services layer automatically denormalized the blob filename into the media record (e.g. via event handler). Even if you don't use the filename to sort, it's often useful to display in search results and the sidebar.

The stuff John described is what we could do in the short term, but it's pretty clunky. First of all, the data model is broken. What if a media record is related to multiple objects, and it should show up first in one, but not the other? The ordering field properly belongs on the relation record. If we had that field, we could implement drag-and-drop reordering somewhere; possibly, in the media snapshot browser itself.

Ray

On Fri, Feb 5, 2016 at 10:36 AM, Richard Millet <richard.millet@lyrasis.orgmailto:richard.millet@lyrasis.org> wrote:

Thanks John.  Do you think this is something that could/should be contributed to the core code?  If so, Megan and the Functional Working group could approve and review the idea and then a pull request could be made to the core repository.

From: Talk <talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org> on behalf of John B Lowe <jblowe@berkeley.edumailto:jblowe@berkeley.edu>
Sent: Friday, February 05, 2016 10:25 AM
To: Kara Vetter
Cc: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org
Subject: Re: [Talk] Ordering Media Snapshot view

Kara,

In fact, there are two different solutions to this problem in use in the UCB deployments:

  • A checkbox on Media records that sets a image as "primary". This does not specify an order for other images associated with an objects (This is deployed for PAHMA).

  • A "page number" field on Media records that does what you seem to need: allows the user to specify an ordering of images. (This is deployed for BAMPFA.)

We have a request for one of these two functionalities from the UC Botanical Garden, and we in the throes of deciding which of the two functionalities will best meet their needs.

The current request is:

https://issues.collectionspace.org/browse/UCBG-431

I'll try to update that with the related issues for completeness.

The point is, the code has been written to do this, and your deployment could be customized to include it...

Regards,

John

On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE <sstone@berkeley.edumailto:sstone@berkeley.edu> wrote:
Kara,

As Aron mentions, I also know of several collections who want this functionality--looks like I reported it a long time ago. These collections have added a primary image flag in their custom fields, but it is just informative--it doesn't make that image appear first. But I think you can modify the record of the one you want to appear first--even if it is a bogus change.

Please vote for the old issue Aron points out.

Susan

On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.orgmailto:kvetter@museumofman.org> wrote:
Hello all!!

So it appears that the Media Snapshot view for multiple images linked to a record are ordered by “Modified Date” rather than by file name.  Is there a known fix or data entry method that will help us overcome this when we want to designate a specific image as the first viewed image in the snapshot?

FYI, we currently title our records using an “_#” system.  E.g. 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view.

It would be nice if there was an option, kind of like a radial dial to select which image is primary once linked to a record but I know that’s a complicated thing to create.

Any thoughts are appreciated.

Kara S. Vetter | Registrar
San Diego Museum of Man
1350 El Prado, Balboa Park | San Diego, CA 92101
619-239-2001, ext 44tel:619-239-2001%2C%20ext%2044 | kvetter@museumofman.orgmailto:kvetter@museumofman.org

Race: Are We So Different?http://www.museumofman.org/exhibit/race-are-we-so-different
Join us for an eye-opening look at
the reality – and unreality – of race.

Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Thanks for bringing up the relation record, Ray. It was present in our earliest wireframes, and would also be useful for typing relationships. Megan Forbes CollectionSpace Program Manager megan.forbes@lyrasis.org 917.267.9676 Cell meganbforbes Skype ________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Ray Lee <rhlee@berkeley.edu> Sent: Friday, February 5, 2016 2:19 PM To: Richard Millet Cc: talk@lists.collectionspace.org Subject: Re: [Talk] Ordering Media Snapshot view As a default I think it should sort by filename. I suspect that would satisfy most people. This would be trivial if the filename were returned in media list results -- but the filename is on the blob record, not the media record. It would be nice if the services layer automatically denormalized the blob filename into the media record (e.g. via event handler). Even if you don't use the filename to sort, it's often useful to display in search results and the sidebar. The stuff John described is what we could do in the short term, but it's pretty clunky. First of all, the data model is broken. What if a media record is related to multiple objects, and it should show up first in one, but not the other? The ordering field properly belongs on the relation record. If we had that field, we could implement drag-and-drop reordering somewhere; possibly, in the media snapshot browser itself. Ray On Fri, Feb 5, 2016 at 10:36 AM, Richard Millet <richard.millet@lyrasis.org<mailto:richard.millet@lyrasis.org>> wrote: Thanks John. Do you think this is something that could/should be contributed to the core code? If so, Megan and the Functional Working group could approve and review the idea and then a pull request could be made to the core repository. ________________________________ From: Talk <talk-bounces@lists.collectionspace.org<mailto:talk-bounces@lists.collectionspace.org>> on behalf of John B Lowe <jblowe@berkeley.edu<mailto:jblowe@berkeley.edu>> Sent: Friday, February 05, 2016 10:25 AM To: Kara Vetter Cc: talk@lists.collectionspace.org<mailto:talk@lists.collectionspace.org> Subject: Re: [Talk] Ordering Media Snapshot view Kara, In fact, there are two different solutions to this problem in use in the UCB deployments: * A checkbox on Media records that sets a image as "primary". This does not specify an order for other images associated with an objects (This is deployed for PAHMA). * A "page number" field on Media records that does what you seem to need: allows the user to specify an ordering of images. (This is deployed for BAMPFA.) We have a request for one of these two functionalities from the UC Botanical Garden, and we in the throes of deciding which of the two functionalities will best meet their needs. The current request is: https://issues.collectionspace.org/browse/UCBG-431 I'll try to update that with the related issues for completeness. The point is, the code has been written to do this, and your deployment could be customized to include it... Regards, John On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE <sstone@berkeley.edu<mailto:sstone@berkeley.edu>> wrote: Kara, As Aron mentions, I also know of several collections who want this functionality--looks like I reported it a long time ago. These collections have added a primary image flag in their custom fields, but it is just informative--it doesn't make that image appear first. But I think you can modify the record of the one you want to appear first--even if it is a bogus change. Please vote for the old issue Aron points out. Susan On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.org<mailto:kvetter@museumofman.org>> wrote: Hello all!! So it appears that the Media Snapshot view for multiple images linked to a record are ordered by “Modified Date” rather than by file name. Is there a known fix or data entry method that will help us overcome this when we want to designate a specific image as the first viewed image in the snapshot? FYI, we currently title our records using an “_#” system. E.g. 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view. It would be nice if there was an option, kind of like a radial dial to select which image is primary once linked to a record but I know that’s a complicated thing to create. Any thoughts are appreciated. Kara S. Vetter | Registrar San Diego Museum of Man 1350 El Prado, Balboa Park | San Diego, CA 92101 619-239-2001, ext 44<tel:619-239-2001%2C%20ext%2044> | kvetter@museumofman.org<mailto:kvetter@museumofman.org> Race: Are We So Different?<http://www.museumofman.org/exhibit/race-are-we-so-different> Join us for an eye-opening look at the reality – and unreality – of race. _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
SS
Susan STONE
Fri, Feb 5, 2016 11:38 PM

In addition multiple people have wanted to be able to add a note to a
relation (rather than to the things being related.)

Susan
On Feb 5, 2016 12:20 PM, "Megan Forbes" megan.forbes@lyrasis.org wrote:

Thanks for bringing up the relation record, Ray. It was present in our
earliest wireframes, and would also be useful for typing relationships.

Megan Forbes
CollectionSpace Program Manager
megan.forbes@lyrasis.org megan.forbes@lyrasis.org
917.267.9676 Cell
meganbforbes Skype

From: Talk talk-bounces@lists.collectionspace.org on behalf of Ray
Lee rhlee@berkeley.edu
Sent: Friday, February 5, 2016 2:19 PM
To: Richard Millet
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Ordering Media Snapshot view

As a default I think it should sort by filename. I suspect that would
satisfy most people. This would be trivial if the filename were returned in
media list results -- but the filename is on the blob record, not the media
record. It would be nice if the services layer automatically denormalized
the blob filename into the media record (e.g. via event handler). Even if
you don't use the filename to sort, it's often useful to display in search
results and the sidebar.

The stuff John described is what we could do in the short term, but it's
pretty clunky. First of all, the data model is broken. What if a media
record is related to multiple objects, and it should show up first in one,
but not the other? The ordering field properly belongs on the relation
record. If we had that field, we could implement drag-and-drop reordering
somewhere; possibly, in the media snapshot browser itself.

Ray

On Fri, Feb 5, 2016 at 10:36 AM, Richard Millet <
richard.millet@lyrasis.org> wrote:

Thanks John.  Do you think this is something that could/should be
contributed to the core code?  If so, Megan and the Functional Working
group could approve and review the idea and then a pull request could be
made to the core repository.

From: Talk talk-bounces@lists.collectionspace.org on behalf of John
B Lowe jblowe@berkeley.edu
Sent: Friday, February 05, 2016 10:25 AM
To: Kara Vetter
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Ordering Media Snapshot view

Kara,

In fact, there are two different solutions to this problem in use in the
UCB deployments:

  • A checkbox on Media records that sets a image as "primary". This does
    not specify an order for other images associated with an objects (This is
    deployed for PAHMA).

  • A "page number" field on Media records that does what you seem to need:
    allows the user to specify an ordering of images. (This is deployed for
    BAMPFA.)

We have a request for one of these two functionalities from the UC
Botanical Garden, and we in the throes of deciding which of the two
functionalities will best meet their needs.

The current request is:

https://issues.collectionspace.org/browse/UCBG-431

I'll try to update that with the related issues for completeness.

The point is, the code has been written to do this, and your deployment
could be customized to include it...

Regards,

John

On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE sstone@berkeley.edu wrote:

Kara,

As Aron mentions, I also know of several collections who want this
functionality--looks like I reported it a long time ago. These collections
have added a primary image flag in their custom fields, but it is just
informative--it doesn't make that image appear first. But I think you can
modify the record of the one you want to appear first--even if it is a
bogus change.

Please vote for the old issue Aron points out.

Susan

On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter kvetter@museumofman.org
wrote:

Hello all!!

So it appears that the Media Snapshot view for multiple images linked
to a record are ordered by “Modified Date” rather than by file name.  Is
there a known fix or data entry method that will help us overcome this when
we want to designate a specific image as the first viewed image in the
snapshot?

FYI, we currently title our records using an “_#” system.  E.g.
1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view.

It would be nice if there was an option, kind of like a radial dial to
select which image is primary once linked to a record but I know that’s a
complicated thing to create.

Any thoughts are appreciated.

Kara S. Vetter | Registrar

San Diego Museum of Man

1350 El Prado, Balboa Park | San Diego, CA 92101

619-239-2001, ext 44 | kvetter@museumofman.org

Race: Are We So Different?
http://www.museumofman.org/exhibit/race-are-we-so-different

Join us for an eye-opening look at

the reality – and unreality – of race.

Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

In addition multiple people have wanted to be able to add a note to a relation (rather than to the things being related.) Susan On Feb 5, 2016 12:20 PM, "Megan Forbes" <megan.forbes@lyrasis.org> wrote: > Thanks for bringing up the relation record, Ray. It was present in our > earliest wireframes, and would also be useful for typing relationships. > > > Megan Forbes > CollectionSpace Program Manager > *megan.forbes@lyrasis.org <megan.forbes@lyrasis.org>* > 917.267.9676 Cell > meganbforbes Skype > > > > > ------------------------------ > *From:* Talk <talk-bounces@lists.collectionspace.org> on behalf of Ray > Lee <rhlee@berkeley.edu> > *Sent:* Friday, February 5, 2016 2:19 PM > *To:* Richard Millet > *Cc:* talk@lists.collectionspace.org > *Subject:* Re: [Talk] Ordering Media Snapshot view > > As a default I think it should sort by filename. I suspect that would > satisfy most people. This would be trivial if the filename were returned in > media list results -- but the filename is on the blob record, not the media > record. It would be nice if the services layer automatically denormalized > the blob filename into the media record (e.g. via event handler). Even if > you don't use the filename to sort, it's often useful to display in search > results and the sidebar. > > The stuff John described is what we could do in the short term, but it's > pretty clunky. First of all, the data model is broken. What if a media > record is related to multiple objects, and it should show up first in one, > but not the other? The ordering field properly belongs on the relation > record. If we had that field, we could implement drag-and-drop reordering > somewhere; possibly, in the media snapshot browser itself. > > Ray > > > On Fri, Feb 5, 2016 at 10:36 AM, Richard Millet < > richard.millet@lyrasis.org> wrote: > >> Thanks John. Do you think this is something that could/should be >> contributed to the core code? If so, Megan and the Functional Working >> group could approve and review the idea and then a pull request could be >> made to the core repository. >> >> >> ------------------------------ >> *From:* Talk <talk-bounces@lists.collectionspace.org> on behalf of John >> B Lowe <jblowe@berkeley.edu> >> *Sent:* Friday, February 05, 2016 10:25 AM >> *To:* Kara Vetter >> *Cc:* talk@lists.collectionspace.org >> *Subject:* Re: [Talk] Ordering Media Snapshot view >> >> Kara, >> >> In fact, there are two different solutions to this problem in use in the >> UCB deployments: >> >> * A checkbox on Media records that sets a image as "primary". This does >> not specify an order for other images associated with an objects (This is >> deployed for PAHMA). >> >> * A "page number" field on Media records that does what you seem to need: >> allows the user to specify an ordering of images. (This is deployed for >> BAMPFA.) >> >> We have a request for one of these two functionalities from the UC >> Botanical Garden, and we in the throes of deciding which of the two >> functionalities will best meet their needs. >> >> The current request is: >> >> https://issues.collectionspace.org/browse/UCBG-431 >> >> I'll try to update that with the related issues for completeness. >> >> The point is, the code has been written to do this, and your deployment >> could be customized to include it... >> >> Regards, >> >> John >> >> On Fri, Feb 5, 2016 at 10:02 AM, Susan STONE <sstone@berkeley.edu> wrote: >> >>> Kara, >>> >>> As Aron mentions, I also know of several collections who want this >>> functionality--looks like I reported it a long time ago. These collections >>> have added a primary image flag in their custom fields, but it is just >>> informative--it doesn't make that image appear first. But I think you can >>> modify the record of the one you want to appear first--even if it is a >>> bogus change. >>> >>> Please vote for the old issue Aron points out. >>> >>> Susan >>> >>> On Fri, Feb 5, 2016 at 9:23 AM, Kara Vetter <kvetter@museumofman.org> >>> wrote: >>> >>>> Hello all!! >>>> >>>> >>>> >>>> So it appears that the Media Snapshot view for multiple images linked >>>> to a record are ordered by “Modified Date” rather than by file name. Is >>>> there a known fix or data entry method that will help us overcome this when >>>> we want to designate a specific image as the first viewed image in the >>>> snapshot? >>>> >>>> >>>> >>>> FYI, we currently title our records using an “_#” system. E.g. >>>> 1931.002.0005_1 is the first view and 1931.002.0005_2 is the second view. >>>> >>>> >>>> >>>> It would be nice if there was an option, kind of like a radial dial to >>>> select which image is primary once linked to a record but I know that’s a >>>> complicated thing to create. >>>> >>>> >>>> >>>> Any thoughts are appreciated. >>>> >>>> >>>> >>>> Kara S. Vetter | Registrar >>>> >>>> San Diego Museum of Man >>>> >>>> 1350 El Prado, Balboa Park | San Diego, CA 92101 >>>> >>>> 619-239-2001, ext 44 | kvetter@museumofman.org >>>> >>>> >>>> >>>> *Race: Are We So Different?* >>>> <http://www.museumofman.org/exhibit/race-are-we-so-different> >>>> >>>> Join us for an eye-opening look at >>>> >>>> the reality – and unreality – of race. >>>> >>>> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >>>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >>> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >
Empathy v1.0   2025 ©emwd.com
Documentation