talk@lists.collectionspace.org
WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsProposal for a contribution to v3.2.3
Hi all,
UC Berkeley is building some functionality for local deployments that we think would be a good addition to the core system. We're calling this the "Show related objects" button. What it will do is this: From a procedure record (such as a Loan Out) that has related Collection Objects, the user will be able to click a "Show" button. Clicking the "Show" button will redirect the user to the Advanced Search results screen with the related Collection Objects listed as if one had done a search for them. From that point, the user can navigate through those Collection Objects. Our production deployments are eager to have capabilities that help them process related objects in more efficient ways.
This functionality is documented in the following Jira and its subtasks:
http://issues.collectionspace.org/browse/PAHMA-762
The UI mockup is attached to:
http://issues.collectionspace.org/browse/PAHMA-766
UC Berkeley proposes that this change be done in the next 2-4 weeks and be built as version 3.2.3 of CollectionSpace. Please send comments or questions to the list or to me. We'll wait to hear from Megan to see if the project is willing to accept this contribution.
Regards,
Chris
P.S. The "Show Related Objects" button will be made even more powerful when UCB contributes some local work done months ago. We will try to contribute that within the next six months.
Chris Hoffman, Ph.D.
Manager of Informatics Services
IST-Research Information Technologies, UC Berkeley
chris.hoffman@berkeley.edu
510-642-9643
Hi Chris,
The "search across record types" functionality is something we see as essential for day to day use of the system, so anything supporting this would be a great improvement. The kind of use case we have in mind is where you could search for all cataloging records containing a reference to a person who was living during a certain period, for example. Will your contributions support this kind of functionality?
This specific button, we don't entirely understand, as the related records tabs and the links on the right side bar appear to already provide these same results. In the example you provide, wouldn't you get the same results by clicking the 'cataloguing' tab? Or is the idea that you have a requirement to see all record types together (cataloguing + media + loan in etc) in one list in order to achieve a quicker overview (and if so, don't you already get this in the 'Action Records' links)?
BTW thanks for shouting out with these proposals.
Cheers,
Chris
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Chris Hoffman
Sendt: 16. april 2013 22:44
Til: talk@lists.collectionspace.org List
Emne: [Talk] Proposal for a contribution to v3.2.3
Hi all,
UC Berkeley is building some functionality for local deployments that we think would be a good addition to the core system. We're calling this the "Show related objects" button. What it will do is this: From a procedure record (such as a Loan Out) that has related Collection Objects, the user will be able to click a "Show" button. Clicking the "Show" button will redirect the user to the Advanced Search results screen with the related Collection Objects listed as if one had done a search for them. From that point, the user can navigate through those Collection Objects. Our production deployments are eager to have capabilities that help them process related objects in more efficient ways.
This functionality is documented in the following Jira and its subtasks:
http://issues.collectionspace.org/browse/PAHMA-762
The UI mockup is attached to:
http://issues.collectionspace.org/browse/PAHMA-766
UC Berkeley proposes that this change be done in the next 2-4 weeks and be built as version 3.2.3 of CollectionSpace. Please send comments or questions to the list or to me. We'll wait to hear from Megan to see if the project is willing to accept this contribution.
Regards,
Chris
P.S. The "Show Related Objects" button will be made even more powerful when UCB contributes some local work done months ago. We will try to contribute that within the next six months.
Chris Hoffman, Ph.D.
Manager of Informatics Services
IST-Research Information Technologies, UC Berkeley
chris.hoffman@berkeley.edumailto:chris.hoffman@berkeley.edu
510-642-9643
Hi Chris,
Megan brought up this point as well. Until we contribute some additional functionality developed at Berkeley, this button wouldn't really do that much.
On the Advanced Search results screen, we've already added a button called "Add to record". It opens a pop up that allows you to search for an existing procedure record and then relate the items in your search to that procedure record. Here's how Michael Black and PAHMA use this extensively: Do an advanced search on Collection Objects. Click "Add to Record". Find an existing Group. Add the search results to the Group. Go to the Group. Run one of many reports we've built for Groups, or just use that to Group to make it easier to navigate through the related objects.
PAHMA wants to be able to run these same reports for all objects related to any procedure.
Still, the Add to Record functionality is very useful because it allows them to create ad-hoc groups more easily. One of the other requests here is to enhance Search to Relate to use Advanced Search, instead of keyword search.
The "Show Related Objects" button is kind of a workaround in this regard and doesn't address the kind of search you mentioned in your first paragraph.
I can see now though that this contribution doesn't add much without the "Add to Record" button. I'll ask my team if we can contribute both things together for 3.2.3. If not, we'll find a later date to contribute these things together.
This
Thanks,
Chris
On Apr 23, 2013, at 1:32 AM, Christopher Pott wrote:
Hi Chris,
The ”search across record types” functionality is something we see as essential for day to day use of the system, so anything supporting this would be a great improvement. The kind of use case we have in mind is where you could search for all cataloging records containing a reference to a person who was living during a certain period, for example. Will your contributions support this kind of functionality?
This specific button, we don’t entirely understand, as the related records tabs and the links on the right side bar appear to already provide these same results. In the example you provide, wouldn’t you get the same results by clicking the ‘cataloguing’ tab? Or is the idea that you have a requirement to see all record types together (cataloguing + media + loan in etc) in one list in order to achieve a quicker overview (and if so, don’t you already get this in the ‘Action Records’ links)?
BTW thanks for shouting out with these proposals.
Cheers,
Chris
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Chris Hoffman
Sendt: 16. april 2013 22:44
Til: talk@lists.collectionspace.org List
Emne: [Talk] Proposal for a contribution to v3.2.3
Hi all,
UC Berkeley is building some functionality for local deployments that we think would be a good addition to the core system. We're calling this the "Show related objects" button. What it will do is this: From a procedure record (such as a Loan Out) that has related Collection Objects, the user will be able to click a "Show" button. Clicking the "Show" button will redirect the user to the Advanced Search results screen with the related Collection Objects listed as if one had done a search for them. From that point, the user can navigate through those Collection Objects. Our production deployments are eager to have capabilities that help them process related objects in more efficient ways.
This functionality is documented in the following Jira and its subtasks:
http://issues.collectionspace.org/browse/PAHMA-762
The UI mockup is attached to:
http://issues.collectionspace.org/browse/PAHMA-766
UC Berkeley proposes that this change be done in the next 2-4 weeks and be built as version 3.2.3 of CollectionSpace. Please send comments or questions to the list or to me. We'll wait to hear from Megan to see if the project is willing to accept this contribution.
Regards,
Chris
P.S. The "Show Related Objects" button will be made even more powerful when UCB contributes some local work done months ago. We will try to contribute that within the next six months.
Chris Hoffman, Ph.D.
Manager of Informatics Services
IST-Research Information Technologies, UC Berkeley
chris.hoffman@berkeley.edu
510-642-9643
Some of this is a work-around for the lack of advanced search in the
search-to-relate dialog. Some of it addresses the lack of check-boxes in
search results and the ability to easily invoke a report or batch process
on that selection. It is possible that some work-arounds might disappear
when a more integrated approach is completed.
We have tried to propose approaches that work with the existing model and
implementation as much as possible, but that require minimal investment in
rewriting existing functionality (especially when it involves the UI, where
we have some challenges).
We just do not have the resources to do everything the way we would ideally
like to, and so end up with some of these work arounds. They do work for
our users, and seem like a reasonable compromise for the time being. Not
always pretty, but that’s life.
Patrick
From: Talk [mailto:talk-bounces@lists.collectionspace.org] *On
Behalf Of *Chris
Hoffman
Sent: Tuesday, April 23, 2013 8:56 AM
To: Christopher Pott
Cc: talk@lists.collectionspace.org List
Subject: Re: [Talk] Proposal for a contribution to v3.2.3
Hi Chris,
Megan brought up this point as well. Until we contribute some additional
functionality developed at Berkeley, this button wouldn't really do that
much.
On the Advanced Search results screen, we've already added a button called
"Add to record". It opens a pop up that allows you to search for an
existing procedure record and then relate the items in your search to that
procedure record. Here's how Michael Black and PAHMA use this extensively:
Do an advanced search on Collection Objects. Click "Add to Record". Find
an existing Group. Add the search results to the Group. Go to the Group.
Run one of many reports we've built for Groups, or just use that to Group
to make it easier to navigate through the related objects.
PAHMA wants to be able to run these same reports for all objects related to
any procedure.
Still, the Add to Record functionality is very useful because it allows
them to create ad-hoc groups more easily. One of the other requests here
is to enhance Search to Relate to use Advanced Search, instead of keyword
search.
The "Show Related Objects" button is kind of a workaround in this regard
and doesn't address the kind of search you mentioned in your first
paragraph.
I can see now though that this contribution doesn't add much without the
"Add to Record" button. I'll ask my team if we can contribute both things
together for 3.2.3. If not, we'll find a later date to contribute these
things together.
This
Thanks,
Chris
On Apr 23, 2013, at 1:32 AM, Christopher Pott wrote:
Hi Chris,
The ”search across record types” functionality is something we see as
essential for day to day use of the system, so anything supporting this
would be a great improvement. The kind of use case we have in mind is where
you could search for all cataloging records containing a reference to a
person who was living during a certain period, for example. Will your
contributions support this kind of functionality?
This specific button, we don’t entirely understand, as the related records
tabs and the links on the right side bar appear to already provide these
same results. In the example you provide, wouldn’t you get the same results
by clicking the ‘cataloguing’ tab? Or is the idea that you have a
requirement to see all record types together (cataloguing + media + loan in
etc) in one list in order to achieve a quicker overview (and if so, don’t
you already get this in the ‘Action Records’ links)?
BTW thanks for shouting out with these proposals.
Cheers,
Chris
Fra: Talk [mailto:talk-bounces@lists.collectionspace.orgtalk-bounces@lists.collectionspace.org
] *På vegne af *Chris Hoffman
Sendt: 16. april 2013 22:44
Til: talk@lists.collectionspace.org List
Emne: [Talk] Proposal for a contribution to v3.2.3
Hi all,
UC Berkeley is building some functionality for local deployments that we
think would be a good addition to the core system. We're calling this the
"Show related objects" button. What it will do is this: From a procedure
record (such as a Loan Out) that has related Collection Objects, the user
will be able to click a "Show" button. Clicking the "Show" button will
redirect the user to the Advanced Search results screen with the related
Collection Objects listed as if one had done a search for them. From that
point, the user can navigate through those Collection Objects. Our
production deployments are eager to have capabilities that help them
process related objects in more efficient ways.
This functionality is documented in the following Jira and its subtasks:
http://issues.collectionspace.org/browse/PAHMA-762
The UI mockup is attached to:
http://issues.collectionspace.org/browse/PAHMA-766
UC Berkeley proposes that this change be done in the next 2-4 weeks and be
built as version 3.2.3 of CollectionSpace. Please send comments or
questions to the list or to me. We'll wait to hear from Megan to see if
the project is willing to accept this contribution.
Regards,
Chris
P.S. The "Show Related Objects" button will be made even more powerful when
UCB contributes some local work done months ago. We will try to contribute
that within the next six months.
Chris Hoffman, Ph.D.
Manager of Informatics Services
IST-Research Information Technologies, UC Berkeley
510-642-9643
On Tue, Apr 23, 2013 at 1:32 AM, Christopher Pott
Christopher.Pott@smk.dk wrote:
The kind of use case we have in mind is where
you could search for all cataloging records containing a reference to a
person who was living during a certain period, for example.
If you have relatively few of these rather involved
'cross-record-type' searches - in this case, "return the CSIDs of
CollectionObject/Cataloging records which contain a reference to a
Person record in one or more of their fields, where a specific date or
date range of interest falls within the span of the birth/death dates
of that person" - but the ones you do have are important and/or
frequently used, you could likely do this with:
a) A report
b) A batch job
If you needed the records resulting from that search to be added to
a Group, for instance, so you could perform actions on them, a batch
job might be able to do this. I don't recall off-hand if there's some
way to pass one-time parameters to a batch job, however, much as you
now can pass them to reports.
Aron
Will your
contributions support this kind of functionality?
This specific button, we don’t entirely understand, as the related records
tabs and the links on the right side bar appear to already provide these
same results. In the example you provide, wouldn’t you get the same results
by clicking the ‘cataloguing’ tab? Or is the idea that you have a
requirement to see all record types together (cataloguing + media + loan in
etc) in one list in order to achieve a quicker overview (and if so, don’t
you already get this in the ‘Action Records’ links)?
BTW thanks for shouting out with these proposals.
Cheers,
Chris
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Chris
Hoffman
Sendt: 16. april 2013 22:44
Til: talk@lists.collectionspace.org List
Emne: [Talk] Proposal for a contribution to v3.2.3
Hi all,
UC Berkeley is building some functionality for local deployments that we
think would be a good addition to the core system. We're calling this the
"Show related objects" button. What it will do is this: From a procedure
record (such as a Loan Out) that has related Collection Objects, the user
will be able to click a "Show" button. Clicking the "Show" button will
redirect the user to the Advanced Search results screen with the related
Collection Objects listed as if one had done a search for them. From that
point, the user can navigate through those Collection Objects. Our
production deployments are eager to have capabilities that help them process
related objects in more efficient ways.
This functionality is documented in the following Jira and its subtasks:
http://issues.collectionspace.org/browse/PAHMA-762
The UI mockup is attached to:
http://issues.collectionspace.org/browse/PAHMA-766
UC Berkeley proposes that this change be done in the next 2-4 weeks and be
built as version 3.2.3 of CollectionSpace. Please send comments or questions
to the list or to me. We'll wait to hear from Megan to see if the project
is willing to accept this contribution.
Regards,
Chris
P.S. The "Show Related Objects" button will be made even more powerful when
UCB contributes some local work done months ago. We will try to contribute
that within the next six months.
Chris Hoffman, Ph.D.
Manager of Informatics Services
IST-Research Information Technologies, UC Berkeley
510-642-9643
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
I wrote:
You could likely do this [cross-record-type search to return Cataloging records that reference persons who were alive during a certain era] with:
a) A report
b) A batch job
There's another option, as well:
c) A web-based app ("webapp")
In the UC Berkeley CollectionSpace deployments - two museums launched
in summer 2012 and a third to be launched this month - there are a
fair number of 'webapps' written for special purposes such as these.
They've been written in an in house-developed Python-based framework,
but now are being transitioned to Django, a widely used framework
(also based on Python). My impression is that we have lots to share
with the community about this, once we can get our focus a bit out of
museum launches and upgrades, and release deadlines.
It's also worth mentioning that the search you've mentioned, Chris,
might conceivably be achievable via two existing Services REST API
calls (as yet untried):
- An advanced search on Persons who lived during a date range, which
can return CSIDs and refNames for each such person;
and either of the following, which loop over the Person records
returned to find their referencing Cataloging records:
2a. A keyword search on Cataloging (CollectionObject) records, using
each of those refNames;
or
2b. A 'referencing objects' (refObjs) search for Cataloging records,
using each Person record's CSID.
Aron
On Tue, Apr 23, 2013 at 12:14 PM, Aron Roberts
aron@socrates.berkeley.edu wrote:
On Tue, Apr 23, 2013 at 1:32 AM, Christopher Pott
Christopher.Pott@smk.dk wrote:
The kind of use case we have in mind is where
you could search for all cataloging records containing a reference to a
person who was living during a certain period, for example.
If you have relatively few of these rather involved
'cross-record-type' searches - in this case, "return the CSIDs of
CollectionObject/Cataloging records which contain a reference to a
Person record in one or more of their fields, where a specific date or
date range of interest falls within the span of the birth/death dates
of that person" - but the ones you do have are important and/or
frequently used, you could likely do this with:
a) A report
b) A batch job
If you needed the records resulting from that search to be added to
a Group, for instance, so you could perform actions on them, a batch
job might be able to do this. I don't recall off-hand if there's some
way to pass one-time parameters to a batch job, however, much as you
now can pass them to reports.
Aron
Will your
contributions support this kind of functionality?
This specific button, we don’t entirely understand, as the related records
tabs and the links on the right side bar appear to already provide these
same results. In the example you provide, wouldn’t you get the same results
by clicking the ‘cataloguing’ tab? Or is the idea that you have a
requirement to see all record types together (cataloguing + media + loan in
etc) in one list in order to achieve a quicker overview (and if so, don’t
you already get this in the ‘Action Records’ links)?
BTW thanks for shouting out with these proposals.
Cheers,
Chris
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Chris
Hoffman
Sendt: 16. april 2013 22:44
Til: talk@lists.collectionspace.org List
Emne: [Talk] Proposal for a contribution to v3.2.3
Hi all,
UC Berkeley is building some functionality for local deployments that we
think would be a good addition to the core system. We're calling this the
"Show related objects" button. What it will do is this: From a procedure
record (such as a Loan Out) that has related Collection Objects, the user
will be able to click a "Show" button. Clicking the "Show" button will
redirect the user to the Advanced Search results screen with the related
Collection Objects listed as if one had done a search for them. From that
point, the user can navigate through those Collection Objects. Our
production deployments are eager to have capabilities that help them process
related objects in more efficient ways.
This functionality is documented in the following Jira and its subtasks:
http://issues.collectionspace.org/browse/PAHMA-762
The UI mockup is attached to:
http://issues.collectionspace.org/browse/PAHMA-766
UC Berkeley proposes that this change be done in the next 2-4 weeks and be
built as version 3.2.3 of CollectionSpace. Please send comments or questions
to the list or to me. We'll wait to hear from Megan to see if the project
is willing to accept this contribution.
Regards,
Chris
P.S. The "Show Related Objects" button will be made even more powerful when
UCB contributes some local work done months ago. We will try to contribute
that within the next six months.
Chris Hoffman, Ph.D.
Manager of Informatics Services
IST-Research Information Technologies, UC Berkeley
510-642-9643
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
This reminds me of some of the documentation I put together for MMI some
months back.
In these wiki pages are some techniques of creating complex API calls and
such. Mind you, while much of this may be specific to MMI's schema and
deployment the basic workflow should stay the same. It's old though -- for
v2.6 -- and there may be better or improved ways to handle some of the
workflow issues especially with respect to filtering multiple API calls.
http://wiki.collectionspace.org/display/deploy/MMI+Collection+Browser+Object+Schema+for+2.6
http://wiki.collectionspace.org/display/deploy/MMI+Collection+Browser+Authority+Term+Schema+for+2.6
Hope this can help,
- Jesse
On Tue, Apr 23, 2013 at 3:51 PM, Aron Roberts aron@socrates.berkeley.eduwrote:
It's also worth mentioning that the search you've mentioned, Chris,
might conceivably be achievable via two existing Services REST API
calls (as yet untried):
- An advanced search on Persons who lived during a date range, which
can return CSIDs and refNames for each such person;
and either of the following, which loop over the Person records
returned to find their referencing Cataloging records:
2a. A keyword search on Cataloging (CollectionObject) records, using
each of those refNames;
or
2b. A 'referencing objects' (refObjs) search for Cataloging records,
using each Person record's CSID.
Very cool, Jesse! Some of this documentation, starting at about
half-way down the page, appears to directly pertain to Chris Pott's
use case.
On Tue, Apr 23, 2013 at 1:25 PM, Jesse Martinez mjesse@gmail.com wrote:
This reminds me of some of the documentation I put together for MMI some
months back.
In these wiki pages are some techniques of creating complex API calls and
such. Mind you, while much of this may be specific to MMI's schema and
deployment the basic workflow should stay the same. It's old though -- for
v2.6 -- and there may be better or improved ways to handle some of the
workflow issues especially with respect to filtering multiple API calls.
http://wiki.collectionspace.org/display/deploy/MMI+Collection+Browser+Object+Schema+for+2.6
http://wiki.collectionspace.org/display/deploy/MMI+Collection+Browser+Authority+Term+Schema+for+2.6
Hope this can help,
- Jesse
On Tue, Apr 23, 2013 at 3:51 PM, Aron Roberts aron@socrates.berkeley.edu
wrote:
It's also worth mentioning that the search you've mentioned, Chris,
might conceivably be achievable via two existing Services REST API
calls (as yet untried):
- An advanced search on Persons who lived during a date range, which
can return CSIDs and refNames for each such person;
and either of the following, which loop over the Person records
returned to find their referencing Cataloging records:
2a. A keyword search on Cataloging (CollectionObject) records, using
each of those refNames;
or
2b. A 'referencing objects' (refObjs) search for Cataloging records,
using each Person record's CSID.
Agreed! I'm really glad to see those documents again. I'd looked through them way back when, but now we're getting these requests for these kinds of searches. Interesting.
On Apr 23, 2013, at 1:48 PM, Aron Roberts wrote:
Very cool, Jesse! Some of this documentation, starting at about
half-way down the page, appears to directly pertain to Chris Pott's
use case.
On Tue, Apr 23, 2013 at 1:25 PM, Jesse Martinez mjesse@gmail.com wrote:
This reminds me of some of the documentation I put together for MMI some
months back.
In these wiki pages are some techniques of creating complex API calls and
such. Mind you, while much of this may be specific to MMI's schema and
deployment the basic workflow should stay the same. It's old though -- for
v2.6 -- and there may be better or improved ways to handle some of the
workflow issues especially with respect to filtering multiple API calls.
http://wiki.collectionspace.org/display/deploy/MMI+Collection+Browser+Object+Schema+for+2.6
http://wiki.collectionspace.org/display/deploy/MMI+Collection+Browser+Authority+Term+Schema+for+2.6
Hope this can help,
- Jesse
On Tue, Apr 23, 2013 at 3:51 PM, Aron Roberts aron@socrates.berkeley.edu
wrote:
It's also worth mentioning that the search you've mentioned, Chris,
might conceivably be achievable via two existing Services REST API
calls (as yet untried):
- An advanced search on Persons who lived during a date range, which
can return CSIDs and refNames for each such person;
and either of the following, which loop over the Person records
returned to find their referencing Cataloging records:
2a. A keyword search on Cataloging (CollectionObject) records, using
each of those refNames;
or
2b. A 'referencing objects' (refObjs) search for Cataloging records,
using each Person record's CSID.
Hi Chris,
Ok, I understand where you're coming from now and can see how your approach begins to enable the kind of searching which I imagine many implementers will require (at least we do). The features you describe (especially "Add to record" in Advanced search) would be very useful addition to the platform.
Cheers,
Chris
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 23. april 2013 17:56
Til: Christopher Pott
Cc: talk@lists.collectionspace.org List
Emne: Re: [Talk] Proposal for a contribution to v3.2.3
Hi Chris,
Megan brought up this point as well. Until we contribute some additional functionality developed at Berkeley, this button wouldn't really do that much.
On the Advanced Search results screen, we've already added a button called "Add to record". It opens a pop up that allows you to search for an existing procedure record and then relate the items in your search to that procedure record. Here's how Michael Black and PAHMA use this extensively: Do an advanced search on Collection Objects. Click "Add to Record". Find an existing Group. Add the search results to the Group. Go to the Group. Run one of many reports we've built for Groups, or just use that to Group to make it easier to navigate through the related objects.
PAHMA wants to be able to run these same reports for all objects related to any procedure.
Still, the Add to Record functionality is very useful because it allows them to create ad-hoc groups more easily. One of the other requests here is to enhance Search to Relate to use Advanced Search, instead of keyword search.
The "Show Related Objects" button is kind of a workaround in this regard and doesn't address the kind of search you mentioned in your first paragraph.
I can see now though that this contribution doesn't add much without the "Add to Record" button. I'll ask my team if we can contribute both things together for 3.2.3. If not, we'll find a later date to contribute these things together.
This
Thanks,
Chris
On Apr 23, 2013, at 1:32 AM, Christopher Pott wrote:
Hi Chris,
The "search across record types" functionality is something we see as essential for day to day use of the system, so anything supporting this would be a great improvement. The kind of use case we have in mind is where you could search for all cataloging records containing a reference to a person who was living during a certain period, for example. Will your contributions support this kind of functionality?
This specific button, we don't entirely understand, as the related records tabs and the links on the right side bar appear to already provide these same results. In the example you provide, wouldn't you get the same results by clicking the 'cataloguing' tab? Or is the idea that you have a requirement to see all record types together (cataloguing + media + loan in etc) in one list in order to achieve a quicker overview (and if so, don't you already get this in the 'Action Records' links)?
BTW thanks for shouting out with these proposals.
Cheers,
Chris
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Chris Hoffman
Sendt: 16. april 2013 22:44
Til: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org List
Emne: [Talk] Proposal for a contribution to v3.2.3
Hi all,
UC Berkeley is building some functionality for local deployments that we think would be a good addition to the core system. We're calling this the "Show related objects" button. What it will do is this: From a procedure record (such as a Loan Out) that has related Collection Objects, the user will be able to click a "Show" button. Clicking the "Show" button will redirect the user to the Advanced Search results screen with the related Collection Objects listed as if one had done a search for them. From that point, the user can navigate through those Collection Objects. Our production deployments are eager to have capabilities that help them process related objects in more efficient ways.
This functionality is documented in the following Jira and its subtasks:
http://issues.collectionspace.org/browse/PAHMA-762
The UI mockup is attached to:
http://issues.collectionspace.org/browse/PAHMA-766
UC Berkeley proposes that this change be done in the next 2-4 weeks and be built as version 3.2.3 of CollectionSpace. Please send comments or questions to the list or to me. We'll wait to hear from Megan to see if the project is willing to accept this contribution.
Regards,
Chris
P.S. The "Show Related Objects" button will be made even more powerful when UCB contributes some local work done months ago. We will try to contribute that within the next six months.
Chris Hoffman, Ph.D.
Manager of Informatics Services
IST-Research Information Technologies, UC Berkeley
chris.hoffman@berkeley.edumailto:chris.hoffman@berkeley.edu
510-642-9643