talk@lists.collectionspace.org
WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsBatch Updates
Is there a way that I'm not seeing to perform batch updates through the user interface, or do I still need to go do this manually through postgres? We need to attach an Exhibition record to over 800 catalogue records.
Thanks,
Elayne Glantzberg
Database Administrator
Aquarian Tabernacle Church
HI Elayne,
At UC Berkeley, we’re doing this in a number of different ways.
a) We’ve customized the user interface so that it’s easier to relate the results of a search operation to a procedural record like Exhibitions. It’s a pretty significant and complex customization, but it’s very powerful. If you’re interested, I could ask someone on the UCB team to point you to the github repo.
b) We’ve also built some Django/Python web apps, and I think some of those help with this kind of thing. They are also significant and complex, requiring you to deploy some additional technology.
c) We haven’t related records via SQL calls because there’s quite a lot that happens in the database when you do those actions in the UI. Instead you might write a little script that basically takes the list of cataloging records (their CSID’s) and issues a call to the relevant REST API to relate each one to the appropriate Exhibition record (via its CSID). It’s possible we have some examples in our github repo — I’ll ask our team to look.
d) Sometimes we have students just spend the time to do this — not ideal of course.
I hope this helps though I know nothing in this list is straightforward. Maybe others will contribute their workarounds too.
Thanks,
Chris Hoffman
UC Berkeley
On Jan 15, 2018, at 2:27 PM, Elayne Glantzberg solinox@solinoxenterprises.com wrote:
Is there a way that I'm not seeing to perform batch updates through the user interface, or do I still need to go do this manually through postgres? We need to attach an Exhibition record to over 800 catalogue records.
Thanks,
Elayne Glantzberg
Database Administrator
Aquarian Tabernacle Church
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
So it sounds like doing a SQL query is not recommended for this. I like the idea of having interns do the grunt work; we have folks on work-study scholarships at the seminary who always need work, so that could be useful.
I would be interested in seeing the customization. I've only tweaked our interface in a couple of small places so far, so it wouldn't be difficult I think to implement a big change and then add my tweaks, right? And seeing how that was done would probably help me with making further changes to meet our own needs later on.
Thanks,
Elayne
On Jan 16, 2018 1:42 PM, Chris Hoffman <chris_h@berkeley.edu> wrote:
HI Elayne,
At UC Berkeley, we’re doing this in a number of different ways.
a) We’ve customized the user interface so that it’s easier to relate the results of a search operation to a procedural record like Exhibitions. It’s a pretty significant and complex customization, but it’s very powerful. If you’re interested, I could ask someone on the UCB team to point you to the github repo.
b) We’ve also built some Django/Python web apps, and I think some of those help with this kind of thing. They are also significant and complex, requiring you to deploy some additional technology.
c) We haven’t related records via SQL calls because there’s quite a lot that happens in the database when you do those actions in the UI. Instead you might write a little script that basically takes the list of cataloging records (their CSID’s) and issues a call to the relevant REST API to relate each one to the appropriate Exhibition record (via its CSID). It’s possible we have some examples in our github repo — I’ll ask our team to look.
d) Sometimes we have students just spend the time to do this — not ideal of course.
I hope this helps though I know nothing in this list is straightforward. Maybe others will contribute their workarounds too.
Thanks,
Chris Hoffman
UC Berkeley
On Jan 15, 2018, at 2:27 PM, Elayne Glantzberg <solinox@solinoxenterprises.com> wrote:
Is there a way that I'm not seeing to perform batch updates through the user interface, or do I still need to go do this manually through postgres? We need to attach an Exhibition record to over 800 catalogue records.
Thanks,
Elayne Glantzberg
Database Administrator
Aquarian Tabernacle Church
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Elayne,
Sounds like we think along similar lines. Do it the inefficient way (grunt work) if you need to get this one out the door, but look at the customization to see if it’s a longer term solution. I’ll ask Ray Lee of our team to describe what he did for Berkeley. It might be a set of customizations, but hopefully we have this documented somewhere.
Thanks,
Chris
On Jan 16, 2018, at 11:04 AM, solinox@solinoxenterprises.com wrote:
So it sounds like doing a SQL query is not recommended for this. I like the idea of having interns do the grunt work; we have folks on work-study scholarships at the seminary who always need work, so that could be useful.
I would be interested in seeing the customization. I've only tweaked our interface in a couple of small places so far, so it wouldn't be difficult I think to implement a big change and then add my tweaks, right? And seeing how that was done would probably help me with making further changes to meet our own needs later on.
Thanks,
Elayne
On Jan 16, 2018 1:42 PM, Chris Hoffman chris_h@berkeley.edu wrote:
HI Elayne,
At UC Berkeley, we’re doing this in a number of different ways.
a) We’ve customized the user interface so that it’s easier to relate the results of a search operation to a procedural record like Exhibitions. It’s a pretty significant and complex customization, but it’s very powerful. If you’re interested, I could ask someone on the UCB team to point you to the github repo.
b) We’ve also built some Django/Python web apps, and I think some of those help with this kind of thing. They are also significant and complex, requiring you to deploy some additional technology.
c) We haven’t related records via SQL calls because there’s quite a lot that happens in the database when you do those actions in the UI. Instead you might write a little script that basically takes the list of cataloging records (their CSID’s) and issues a call to the relevant REST API to relate each one to the appropriate Exhibition record (via its CSID). It’s possible we have some examples in our github repo — I’ll ask our team to look.
d) Sometimes we have students just spend the time to do this — not ideal of course.
I hope this helps though I know nothing in this list is straightforward. Maybe others will contribute their workarounds too.
Thanks,
Chris Hoffman
UC Berkeley
On Jan 15, 2018, at 2:27 PM, Elayne Glantzberg <solinox@solinoxenterprises.com mailto:solinox@solinoxenterprises.com> wrote:
Is there a way that I'm not seeing to perform batch updates through the user interface, or do I still need to go do this manually through postgres? We need to attach an Exhibition record to over 800 catalogue records.
Thanks,
Elayne Glantzberg
Database Administrator
Aquarian Tabernacle Church
Talk mailing list
Talk@lists.collectionspace.org mailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Elayne,
If there's an advanced search you can do that will give you the 800 records you're looking to relate, no additional customization is needed to relate them to an existing Exhibition record.
-
Create the exhibition record
-
Run your advanced search
-
Change the "show" number in the results listing to be 50 per page
-
Click "add to record" at the top right of the search results listing
-
Search for the exhibition record you created
-
Select the exhibition record from the search results & click "add search results"
-
The 50 records on your first page of search results will be related
-
You do need to go page by page, but 16 repeated operations is better than 800!
Hope this helps,
Megan
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 solinox@solinoxenterprises.com solinox@solinoxenterprises.com
Sent: Tuesday, January 16, 2018 2:04:17 PM
To: Chris Hoffman
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Batch Updates
So it sounds like doing a SQL query is not recommended for this. I like the idea of having interns do the grunt work; we have folks on work-study scholarships at the seminary who always need work, so that could be useful.
I would be interested in seeing the customization. I've only tweaked our interface in a couple of small places so far, so it wouldn't be difficult I think to implement a big change and then add my tweaks, right? And seeing how that was done would probably help me with making further changes to meet our own needs later on.
Thanks,
Elayne
On Jan 16, 2018 1:42 PM, Chris Hoffman chris_h@berkeley.edu wrote:
HI Elayne,
At UC Berkeley, we’re doing this in a number of different ways.
a) We’ve customized the user interface so that it’s easier to relate the results of a search operation to a procedural record like Exhibitions. It’s a pretty significant and complex customization, but it’s very powerful. If you’re interested, I could ask someone on the UCB team to point you to the github repo.
b) We’ve also built some Django/Python web apps, and I think some of those help with this kind of thing. They are also significant and complex, requiring you to deploy some additional technology.
c) We haven’t related records via SQL calls because there’s quite a lot that happens in the database when you do those actions in the UI. Instead you might write a little script that basically takes the list of cataloging records (their CSID’s) and issues a call to the relevant REST API to relate each one to the appropriate Exhibition record (via its CSID). It’s possible we have some examples in our github repo — I’ll ask our team to look.
d) Sometimes we have students just spend the time to do this — not ideal of course.
I hope this helps though I know nothing in this list is straightforward. Maybe others will contribute their workarounds too.
Thanks,
Chris Hoffman
UC Berkeley
On Jan 15, 2018, at 2:27 PM, Elayne Glantzberg <solinox@solinoxenterprises.commailto:solinox@solinoxenterprises.com> wrote:
Is there a way that I'm not seeing to perform batch updates through the user interface, or do I still need to go do this manually through postgres? We need to attach an Exhibition record to over 800 catalogue records.
Thanks,
Elayne Glantzberg
Database Administrator
Aquarian Tabernacle Church
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
That will do it, thank you, Megan!!
On Jan 16, 2018 2:18 PM, Megan Forbes <megan.forbes@lyrasis.org> wrote:
Elayne,
If there's an advanced search you can do that will give you the 800 records you're looking to relate, no additional customization is needed to relate them to an existing Exhibition record.
- Create the exhibition record
- Run your advanced search
- Change the "show" number in the results listing to be 50 per page
- Click "add to record" at the top right of the search results listing
- Search for the exhibition record you created
- Select the exhibition record from the search results & click "add search results"
- The 50 records on your first page of search results will be related
- You do need to go page by page, but 16 repeated operations is better than 800!
Hope this helps,
Megan
Megan Forbes
CollectionSpace Program Manager
megan.forbes@lyrasis.org
917.267.9676 Cellmeganbforbes Skype
From: Talk <talk-bounces@lists.collectionspace.org> on behalf of solinox@solinoxenterprises.com <solinox@solinoxenterprises.com>
Sent: Tuesday, January 16, 2018 2:04:17 PM
To: Chris Hoffman
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Batch UpdatesSo it sounds like doing a SQL query is not recommended for this. I like the idea of having interns do the grunt work; we have folks on work-study scholarships at the seminary who always need work, so that could be useful.
I would be interested in seeing the customization. I've only tweaked our interface in a couple of small places so far, so it wouldn't be difficult I think to implement a big change and then add my tweaks, right? And seeing how that was done would probably help me with making further changes to meet our own needs later on.
Thanks,
Elayne
On Jan 16, 2018 1:42 PM, Chris Hoffman <chris_h@berkeley.edu> wrote:
HI Elayne,
At UC Berkeley, we’re doing this in a number of different ways.
a) We’ve customized the user interface so that it’s easier to relate the results of a search operation to a procedural record like Exhibitions. It’s a pretty significant and complex customization, but it’s very powerful. If you’re interested, I could ask someone on the UCB team to point you to the github repo.
b) We’ve also built some Django/Python web apps, and I think some of those help with this kind of thing. They are also significant and complex, requiring you to deploy some additional technology.
c) We haven’t related records via SQL calls because there’s quite a lot that happens in the database when you do those actions in the UI. Instead you might write a little script that basically takes the list of cataloging records (their CSID’s) and issues a call to the relevant REST API to relate each one to the appropriate Exhibition record (via its CSID). It’s possible we have some examples in our github repo — I’ll ask our team to look.
d) Sometimes we have students just spend the time to do this — not ideal of course.
I hope this helps though I know nothing in this list is straightforward. Maybe others will contribute their workarounds too.
Thanks,
Chris Hoffman
UC Berkeley
On Jan 15, 2018, at 2:27 PM, Elayne Glantzberg <solinox@solinoxenterprises.com> wrote:
Is there a way that I'm not seeing to perform batch updates through the user interface, or do I still need to go do this manually through postgres? We need to attach an Exhibition record to over 800 catalogue records.
Thanks,
Elayne Glantzberg
Database Administrator
Aquarian Tabernacle Church
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Elayne,
The customization we did at Berkeley that Chris described is in fact the
feature that Megan described. It's been part of the core system for a few
versions now. The only remaining customization we have there is that we
increased the max search result page size to 500, so you don't have to go
through as many pages. This will be moot in 5.0, because the end user can
set the page size to whatever they choose.
Ray
On Tue, Jan 16, 2018 at 11:18 AM, Megan Forbes megan.forbes@lyrasis.org
wrote:
Elayne,
If there's an advanced search you can do that will give you the 800
records you're looking to relate, no additional customization is needed to
relate them to an existing Exhibition record.
-
Create the exhibition record
-
Run your advanced search
-
Change the "show" number in the results listing to be 50 per page
-
Click "add to record" at the top right of the search results listing
-
Search for the exhibition record you created
-
Select the exhibition record from the search results & click "add search
results" -
The 50 records on your first page of search results will be related
-
You do need to go page by page, but 16 repeated operations is better
than 800!
Hope this helps,
Megan
Megan Forbes
CollectionSpace Program Manager
megan.forbes@lyrasis.org megan.forbes@lyrasis.org
917.267.9676 <(917)%20267-9676> Cell
meganbforbes Skype
From: Talk talk-bounces@lists.collectionspace.org on behalf of
solinox@solinoxenterprises.com solinox@solinoxenterprises.com
Sent: Tuesday, January 16, 2018 2:04:17 PM
To: Chris Hoffman
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Batch Updates
So it sounds like doing a SQL query is not recommended for this. I like
the idea of having interns do the grunt work; we have folks on work-study
scholarships at the seminary who always need work, so that could be useful.
I would be interested in seeing the customization. I've only tweaked our
interface in a couple of small places so far, so it wouldn't be difficult I
think to implement a big change and then add my tweaks, right? And seeing
how that was done would probably help me with making further changes to
meet our own needs later on.
Thanks,
Elayne
On Jan 16, 2018 1:42 PM, Chris Hoffman chris_h@berkeley.edu wrote:
HI Elayne,
At UC Berkeley, we’re doing this in a number of different ways.
a) We’ve customized the user interface so that it’s easier to relate the
results of a search operation to a procedural record like Exhibitions.
It’s a pretty significant and complex customization, but it’s very
powerful. If you’re interested, I could ask someone on the UCB team to
point you to the github repo.
b) We’ve also built some Django/Python web apps, and I think some of those
help with this kind of thing. They are also significant and complex,
requiring you to deploy some additional technology.
c) We haven’t related records via SQL calls because there’s quite a lot
that happens in the database when you do those actions in the UI. Instead
you might write a little script that basically takes the list of cataloging
records (their CSID’s) and issues a call to the relevant REST API to relate
each one to the appropriate Exhibition record (via its CSID). It’s possible
we have some examples in our github repo — I’ll ask our team to look.
d) Sometimes we have students just spend the time to do this — not ideal
of course.
I hope this helps though I know nothing in this list is straightforward.
Maybe others will contribute their workarounds too.
Thanks,
Chris Hoffman
UC Berkeley
On Jan 15, 2018, at 2:27 PM, Elayne Glantzberg <
solinox@solinoxenterprises.com> wrote:
Is there a way that I'm not seeing to perform batch updates through the
user interface, or do I still need to go do this manually through postgres?
We need to attach an Exhibition record to over 800 catalogue records.
Thanks,
Elayne Glantzberg
Database Administrator
Aquarian Tabernacle Church
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
Oh, I’d forgotten that this UCB customization has already been added to the core system. Hooray!
Chris
On Jan 16, 2018, at 11:32 AM, solinox@solinoxenterprises.com wrote:
That will do it, thank you, Megan!!
On Jan 16, 2018 2:18 PM, Megan Forbes megan.forbes@lyrasis.org wrote:
Elayne,
If there's an advanced search you can do that will give you the 800 records you're looking to relate, no additional customization is needed to relate them to an existing Exhibition record.
- Create the exhibition record
- Run your advanced search
- Change the "show" number in the results listing to be 50 per page
- Click "add to record" at the top right of the search results listing
- Search for the exhibition record you created
- Select the exhibition record from the search results & click "add search results"
- The 50 records on your first page of search results will be related
- You do need to go page by page, but 16 repeated operations is better than 800!
Hope this helps,
Megan
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 solinox@solinoxenterprises.com solinox@solinoxenterprises.com
Sent: Tuesday, January 16, 2018 2:04:17 PM
To: Chris Hoffman
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Batch Updates
So it sounds like doing a SQL query is not recommended for this. I like the idea of having interns do the grunt work; we have folks on work-study scholarships at the seminary who always need work, so that could be useful.
I would be interested in seeing the customization. I've only tweaked our interface in a couple of small places so far, so it wouldn't be difficult I think to implement a big change and then add my tweaks, right? And seeing how that was done would probably help me with making further changes to meet our own needs later on.
Thanks,
Elayne
On Jan 16, 2018 1:42 PM, Chris Hoffman chris_h@berkeley.edu wrote:
HI Elayne,
At UC Berkeley, we’re doing this in a number of different ways.
a) We’ve customized the user interface so that it’s easier to relate the results of a search operation to a procedural record like Exhibitions. It’s a pretty significant and complex customization, but it’s very powerful. If you’re interested, I could ask someone on the UCB team to point you to the github repo.
b) We’ve also built some Django/Python web apps, and I think some of those help with this kind of thing. They are also significant and complex, requiring you to deploy some additional technology.
c) We haven’t related records via SQL calls because there’s quite a lot that happens in the database when you do those actions in the UI. Instead you might write a little script that basically takes the list of cataloging records (their CSID’s) and issues a call to the relevant REST API to relate each one to the appropriate Exhibition record (via its CSID). It’s possible we have some examples in our github repo — I’ll ask our team to look.
d) Sometimes we have students just spend the time to do this — not ideal of course.
I hope this helps though I know nothing in this list is straightforward. Maybe others will contribute their workarounds too.
Thanks,
Chris Hoffman
UC Berkeley
On Jan 15, 2018, at 2:27 PM, Elayne Glantzberg <solinox@solinoxenterprises.com mailto:solinox@solinoxenterprises.com> wrote:
Is there a way that I'm not seeing to perform batch updates through the user interface, or do I still need to go do this manually through postgres? We need to attach an Exhibition record to over 800 catalogue records.
Thanks,
Elayne Glantzberg
Database Administrator
Aquarian Tabernacle Church
Talk mailing list
Talk@lists.collectionspace.org mailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org