talk@lists.collectionspace.org
WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsLocation/Movement/Inventory Schema Questions
Hi all,
I'd like to ask the implementers to weigh in on two questions that
have come up as we go through Design & Scope week for Location and
Movement upgrades in version 2.3.
First: In October of 2010, SMK requested the addition of the following
fields to the Movement schema:
- Movement Contact and Contact Role: SMK uses Contact as a repeatable
element with an associated role (for example: curatorial contact,
registrar contact, art handler contact). - Move requested by: SMK uses this field to record the person who
requested the move be planned - Moving to location: SMK uses this field to record where the object
will be moved to.
SMK uses Movement Control Information extensively to plan for movement
of works coming into and going out of the museum for loans to
exhibitions. By adding these 4 fields, they believe the Movement
Control Information schema can be used as a complete planning tool.
Point number three is already covered by the new "soft save" and "hard
save" in 2.3: when a user puts in a future date to indicate that a
move is planned, and then puts the "Moving to location" in the Current
location field, and uses "soft save" so that the planned move record
remains editable.
So would others find adding the fields in points one and two helpful,
or are these fields more of an institution-specific extension? Here
at MMI, we don't use CollectionSpace as a planning tool, so it is not
so useful for us.
Second: SMK also asked that there be an "internal" and an "external"
feed for the "Current Location" field. This would mean that the
current location field is fed from both the Storage Location Authority
(internal) and the Organization Authority (external). This would
reflect situations where an object was being loaned to another
institution, for example. This is a situation which we do encounter
here at MMI and I could anticipate being useful.
Please weigh in by This Friday, when Design & Scope week ends for
release 2.3. If we don't hear feedback by then, since these requests
were made so long ago, we will assume that these additions aren't
needed by the community and will not put them on the docket for 2.3.
Thank you!
__
Carly Bogen
Acting Registrar
MUSEUM OF THE MOVING IMAGE
36-01 35 Avenue, Astoria, NY 11106
movingimage.us 718 777 6800
Direct: 718 777 6841
Hi Carly and all,
Since we are discussing Location and Movement, and Inventory - I just want to remind you of a CS wikipage in which PAHMA and we at SMK explained our current procedures in detail. Originally the page was created as responses to inquiries made by Megan.
You'll find it here: http://wiki.collectionspace.org/display/collectionspace/Location%2C+Movement%2C+and+Inventory+Inquiries
Cheers,
Kim
-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Carly Bogen
Sendt: 7. marts 2012 22:36
Til: CollectionSpace Talk List
Emne: [Talk] Location/Movement/Inventory Schema Questions
Hi all,
I'd like to ask the implementers to weigh in on two questions that
have come up as we go through Design & Scope week for Location and
Movement upgrades in version 2.3.
First: In October of 2010, SMK requested the addition of the following
fields to the Movement schema:
- Movement Contact and Contact Role: SMK uses Contact as a repeatable
element with an associated role (for example: curatorial contact,
registrar contact, art handler contact). - Move requested by: SMK uses this field to record the person who
requested the move be planned - Moving to location: SMK uses this field to record where the object
will be moved to.
SMK uses Movement Control Information extensively to plan for movement
of works coming into and going out of the museum for loans to
exhibitions. By adding these 4 fields, they believe the Movement
Control Information schema can be used as a complete planning tool.
Point number three is already covered by the new "soft save" and "hard
save" in 2.3: when a user puts in a future date to indicate that a
move is planned, and then puts the "Moving to location" in the Current
location field, and uses "soft save" so that the planned move record
remains editable.
So would others find adding the fields in points one and two helpful,
or are these fields more of an institution-specific extension? Here
at MMI, we don't use CollectionSpace as a planning tool, so it is not
so useful for us.
Second: SMK also asked that there be an "internal" and an "external"
feed for the "Current Location" field. This would mean that the
current location field is fed from both the Storage Location Authority
(internal) and the Organization Authority (external). This would
reflect situations where an object was being loaned to another
institution, for example. This is a situation which we do encounter
here at MMI and I could anticipate being useful.
Please weigh in by This Friday, when Design & Scope week ends for
release 2.3. If we don't hear feedback by then, since these requests
were made so long ago, we will assume that these additions aren't
needed by the community and will not put them on the docket for 2.3.
Thank you!
__
Carly Bogen
Acting Registrar
MUSEUM OF THE MOVING IMAGE
36-01 35 Avenue, Astoria, NY 11106
movingimage.us 718 777 6800
Direct: 718 777 6841
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Carly,
I overlooked your second question. The internal and external feeds for current location would be hugely helpful for PAHMA. Right now, we have to use a clumsy solution whereby "On Loan" is selected as a location (the top node of our hierarchical locations authority, in fact, is "real locations" versus "non-locations"), and then the actual location of the borrower is entered in a non-controlled notes field. The proposed solution would be a far better fit for PAHMA.
Michael
On Mar 7, 2012, at 1:36 PM, Carly Bogen wrote:
Hi all,
I'd like to ask the implementers to weigh in on two questions that
have come up as we go through Design & Scope week for Location and
Movement upgrades in version 2.3.
First: In October of 2010, SMK requested the addition of the following
fields to the Movement schema:
- Movement Contact and Contact Role: SMK uses Contact as a repeatable
element with an associated role (for example: curatorial contact,
registrar contact, art handler contact). - Move requested by: SMK uses this field to record the person who
requested the move be planned - Moving to location: SMK uses this field to record where the object
will be moved to.
SMK uses Movement Control Information extensively to plan for movement
of works coming into and going out of the museum for loans to
exhibitions. By adding these 4 fields, they believe the Movement
Control Information schema can be used as a complete planning tool.
Point number three is already covered by the new "soft save" and "hard
save" in 2.3: when a user puts in a future date to indicate that a
move is planned, and then puts the "Moving to location" in the Current
location field, and uses "soft save" so that the planned move record
remains editable.
So would others find adding the fields in points one and two helpful,
or are these fields more of an institution-specific extension? Here
at MMI, we don't use CollectionSpace as a planning tool, so it is not
so useful for us.
Second: SMK also asked that there be an "internal" and an "external"
feed for the "Current Location" field. This would mean that the
current location field is fed from both the Storage Location Authority
(internal) and the Organization Authority (external). This would
reflect situations where an object was being loaned to another
institution, for example. This is a situation which we do encounter
here at MMI and I could anticipate being useful.
Please weigh in by This Friday, when Design & Scope week ends for
release 2.3. If we don't hear feedback by then, since these requests
were made so long ago, we will assume that these additions aren't
needed by the community and will not put them on the docket for 2.3.
Thank you!
__
Carly Bogen
Acting Registrar
MUSEUM OF THE MOVING IMAGE
36-01 35 Avenue, Astoria, NY 11106
movingimage.us 718 777 6800
Direct: 718 777 6841
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Thanks everybody for your responses. For the upcoming release, we will
incorporate the request for Current Location to be fed both from the
Storage Location Authority and the Organization Authority. The other
additional fields will not make it into this release, and more
discussion may be warranted to see if they are better fit for a local
extension.
Thanks again!
Carly
Carly Bogen
Acting Registrar
MUSEUM OF THE MOVING IMAGE
36-01 35 Avenue, Astoria, NY 11106
movingimage.us 718 777 6800
Direct: 718 777 6841
On Thu, Mar 8, 2012 at 12:02 PM, Michael T. Black mtblack@berkeley.edu wrote:
Hi Carly,
I overlooked your second question. The internal and external feeds for current location would be hugely helpful for PAHMA. Right now, we have to use a clumsy solution whereby "On Loan" is selected as a location (the top node of our hierarchical locations authority, in fact, is "real locations" versus "non-locations"), and then the actual location of the borrower is entered in a non-controlled notes field. The proposed solution would be a far better fit for PAHMA.
Michael
On Mar 7, 2012, at 1:36 PM, Carly Bogen wrote:
Hi all,
I'd like to ask the implementers to weigh in on two questions that
have come up as we go through Design & Scope week for Location and
Movement upgrades in version 2.3.
First: In October of 2010, SMK requested the addition of the following
fields to the Movement schema:
- Movement Contact and Contact Role: SMK uses Contact as a repeatable
element with an associated role (for example: curatorial contact,
registrar contact, art handler contact). - Move requested by: SMK uses this field to record the person who
requested the move be planned - Moving to location: SMK uses this field to record where the object
will be moved to.
SMK uses Movement Control Information extensively to plan for movement
of works coming into and going out of the museum for loans to
exhibitions. By adding these 4 fields, they believe the Movement
Control Information schema can be used as a complete planning tool.
Point number three is already covered by the new "soft save" and "hard
save" in 2.3: when a user puts in a future date to indicate that a
move is planned, and then puts the "Moving to location" in the Current
location field, and uses "soft save" so that the planned move record
remains editable.
So would others find adding the fields in points one and two helpful,
or are these fields more of an institution-specific extension? Here
at MMI, we don't use CollectionSpace as a planning tool, so it is not
so useful for us.
Second: SMK also asked that there be an "internal" and an "external"
feed for the "Current Location" field. This would mean that the
current location field is fed from both the Storage Location Authority
(internal) and the Organization Authority (external). This would
reflect situations where an object was being loaned to another
institution, for example. This is a situation which we do encounter
here at MMI and I could anticipate being useful.
Please weigh in by This Friday, when Design & Scope week ends for
release 2.3. If we don't hear feedback by then, since these requests
were made so long ago, we will assume that these additions aren't
needed by the community and will not put them on the docket for 2.3.
Thank you!
__
Carly Bogen
Acting Registrar
MUSEUM OF THE MOVING IMAGE
36-01 35 Avenue, Astoria, NY 11106
movingimage.us 718 777 6800
Direct: 718 777 6841
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org