Issue 48 in gref-mvz: Link from collecting event to Arctos

1 view
Skip to first unread message

codesite...@google.com

unread,
May 5, 2008, 6:01:32 PM5/5/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

New issue report by zylorian:
What steps will reproduce the problem?
1. Find a collecting event on a GReF page
2.
3.

What is the expected output? What do you see instead?
Want a link to
http://mvzarctos.berkeley.edu/Locality.cfm?Action=editCollEvnt&collecting_event_id=<the
collecting event>

Please use labels and text to provide additional information.
Doris, I want you to work on this.


Issue attributes:
Status: New
Owner: zylorian
CC: carlacic, DKThung, eightysteele
Labels: Type-Enhancement Priority-Medium

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

codesite...@google.com

unread,
May 5, 2008, 6:05:33 PM5/5/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #1 by eightysteele:
peter, please specify the query needed for getting the collecting event id.


Issue attribute updates:
Labels: Usability

codesite...@google.com

unread,
May 5, 2008, 6:09:34 PM5/5/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #2 by zylorian:
Reciprocal link from Arctos back to here is Arctos issue 92.

codesite...@google.com

unread,
May 5, 2008, 6:13:35 PM5/5/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #3 by zylorian:
Reciprocal link from Arctos back to here is <a
href="http://code.google.com/p/arctos/issues/detail?id=92">Arctos issue 92</a>.

codesite...@google.com

unread,
May 5, 2008, 6:17:36 PM5/5/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #4 by zylorian:


Reciprocal link from Arctos back to here is

http://code.google.com/p/arctos/issues/detail?id=92

codesite...@google.com

unread,
May 5, 2008, 6:21:37 PM5/5/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #5 by zylorian:
Try looking at:
{{{
org.mvz.gref.client.widgets.ROICatalogNumberDisplay
org.mvz.gref.datamodel.ROICatalogNumberValue
}}}
for an example on how to do the URL. Look especially at
org.mvz.gref.datamodel.ROICatalogNumberValue's getURL() method.

You will want to implement it for:
{{{
org.mvz.gref.client.widgets.ROICollectingEventDisplay
org.mvz.gref.datamodel.ROICollectingEventValue

codesite...@google.com

unread,
May 5, 2008, 6:25:38 PM5/5/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #6 by zylorian:

codesite...@google.com

unread,
May 7, 2008, 2:24:46 PM5/7/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #7 by zylorian:
Make it appear only for gref users with certain access. Since gref does not
distinguish between different logged in users, just make it so that you
can only see
this link if you are logged in, and the people who care to use it will
use it.

Summary: if logged in, show link. if not logged in, don't show the link.

codesite...@google.com

unread,
May 7, 2008, 2:28:46 PM5/7/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #8 by carlacic:
Why restrict it to logged in users? I think it should be available to
any user.

codesite...@google.com

unread,
May 7, 2008, 2:37:50 PM5/7/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #9 by zylorian:
If you want it to be available to any user, then don't make the link to
a restricted
page, that is, the edit collecting event page.

Make it link to, say,
http://mvzarctos-dev.berkeley.edu/SpecimenResults.cfm?collecting_event_id=110941

If the curator wants to edit the collecting event, then have them go to
the specimen,
click edit collecting event, and go from there.

codesite...@google.com

unread,
May 7, 2008, 2:41:51 PM5/7/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #10 by eightysteele:
this is a good approach. carla?

codesite...@google.com

unread,
May 7, 2008, 3:55:17 PM5/7/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #11 by carlacic:
Agreed, this does make more sense. Thanks, Peter!

codesite...@google.com

unread,
May 7, 2008, 4:18:24 PM5/7/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #12 by eightysteele:
(No comment was entered for this change.)


Issue attribute updates:
Status: Accepted

codesite...@google.com

unread,
May 7, 2008, 4:22:25 PM5/7/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #13 by eightysteele:


(No comment was entered for this change.)


Issue attribute updates:
Labels: Milestone-Release1.0.6

codesite...@google.com

unread,
May 12, 2008, 2:33:57 PM5/12/08
to gr...@googlegroups.com
Issue 48: Link from collecting event to Arctos
http://code.google.com/p/gref-mvz/issues/detail?id=48

Comment #14 by DKThung:
On page that has collecting Event, expanding with more details should
show a
collectingEvent row with either a collecting event id or nothing at
all(if no id was
found). Clicking on the id should link to
http://mvzarctos-dev.berkeley.edu/SpecimenResults.cfm?collecting_event_id=110941

Reply all
Reply to author
Forward
0 new messages