Hi

Below You will find some comments from looking at 0.1 and 0.2

/hans r

collectionspace

feedback and comments from Hans Rengman, META, Sweden - hans@meta.se

0.1

swedish diacritic characters "åäö" seems to work fine from my environment
(PC - win xp - Firefox)
http://demo.collectionspace.org:8080/cspace-ui/html/objectentry.html?objectId=12345

but not from Murberget , county museum of wasternorrland
()
http://demo.collectionspace.org:8080/cspace-ui/html/objectentry.html?objectId=m45.56

ACCESSION NUMBER

the history/tradition of giving "accession
number"/"inventory number" is not that
standardised here as it might look from Your examples and guidelines:
1
year.acquisition.number.part - systems with variations

2
a clean series of running numbers (MM12345)

3
other locally defined structure. (including
letters showing parts of collections etc as part
of the number.) (including /-_&% etc which might be system critic symbols)

1 and 3 forms a djungle and might not be as
structured as it looks at the first -

The discussion since 1980-ies form two schools,
either that the number is just an identifier of
the object - bearing no coded information. This
viewpoint is furthermore avoiding subnumbers as
long as possible. You can find this model
represented in quite a lot of regional museums.
...or the more structured (rigid) way of
presuming a pre-knowledge in interpreting information.

Related to this is the numbering of images of
objects - where museums either use the object
accession nr as identity for the first image,
then adding .a or .1 or other suffix for extra
images OR maintaining images in a serie of its
own with structured or running number format -

Analysis:
Experiences tells us that accession number/
inventory number fields MUST be handled as a free
format - (or even better - possible to local
customisation (like the "system generated number
setup" -  of input rules (more than one syntax
allowed since routines have changed over time)

...and that object id-number and images id-number
(free format) must be possible to interconnect in many-to-many relationships.

===================

0.2

Very comprehensive forms - There is a lot of
terms which are not intuitive in english to a
swedish user - I think this points to two problem areas.
1
"real" translation - finding wlee vorking equivalents to terminology used...

2
discussing "cultural" differences in context and
concept - curatorial traditions and legal issues colouring terminology.

I will gladly take part in these areas!
a "wordbook" of system terminology acn
be useful for interoperability.

=========================
hans rengman

• META - Kunskap om kunskap                      Hans Rengman  *
  '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
• www.meta.se                                  hans@meta.se  *

•                                                           *
  

• Hovslagaregatan 11            tel:  +46 (0)522 - 51 10 94  *
• SE-451 44 Uddevalla                                          *
• Sweden                        GSM:  +46 (0)70 - 718 23 25  *
  ***********  P  Please consider the environment
  before printing this e-mail    ************

Great feedback - thanks Hans.

I'll respond to a few items, and let others jump in on the rest.

We definitely support different patterns for things like accession numbers,
and you will see this exposed in upcoming releases. Each museum can define
their own patterns for most ids.

Forms customization: it will be straightforward to change the fields shown
in a given form, and to change the labels on those fields. We're working on
the details now.

I think that in advance of full translations of the tool, it is a great idea
to begin compiling a list of common terms and field labels, with
translations to other languages. This could be maintained on our wiki by the
community, and will then be incorporated into the configuration files to
support localized versions of the application.

Megan/Anastasia - what do you think about this?

Patrick

From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Hans Rengman
Sent: Wednesday, October 21, 2009 11:46 PM
To: talk@lists.collectionspace.org
Subject: [Talk] feedback

Hi

Below You will find some comments from looking at 0.1 and 0.2

/hans r

collectionspace

feedback and comments from Hans Rengman, META, Sweden - hans@meta.se

0.1

swedish diacritic characters "åäö" seems to work fine from my environment
(PC - win xp - Firefox)
http://demo.collectionspace.org:8080/cspace-ui/html/objectentry.html?objectI
d=12345

but not from Murberget , county museum of wasternorrland
()
http://demo.collectionspace.org:8080/cspace-ui/html/objectentry.html?objectI
d=m45.56

ACCESSION NUMBER

the history/tradition of giving "accession number"/"inventory number" is
not that standardised here as it might look from Your examples and
guidelines:
1
year.acquisition.number.part - systems with variations

2
a clean series of running numbers (MM12345)

3
other locally defined structure. (including letters showing parts of
collections etc as part of the number.) (including /-_&% etc which might be
system critic symbols)

1 and 3 forms a djungle and might not be as structured as it looks at the
first -

The discussion since 1980-ies form two schools, either that the number is
just an identifier of the object - bearing no coded information. This
viewpoint is furthermore avoiding subnumbers as long as possible. You can
find this model represented in quite a lot of regional museums. ...or the
more structured (rigid) way of presuming a pre-knowledge in interpreting
information.

Related to this is the numbering of images of objects - where museums either
use the object accession nr as identity for the first image, then adding .a
or .1 or other suffix for extra images OR maintaining images in a serie of
its own with structured or running number format -

Analysis:
Experiences tells us that accession number/ inventory number fields MUST be
handled as a free format - (or even better - possible to local customisation
(like the "system generated number setup" -  of input rules (more than one
syntax allowed since routines have changed over time)

...and that object id-number and images id-number (free format) must be
possible to interconnect in many-to-many relationships.

===================

0.2

Very comprehensive forms - There is a lot of terms which are not intuitive
in english to a swedish user - I think this points to two problem areas.
1
"real" translation - finding wlee vorking equivalents to terminology used...

2
discussing "cultural" differences in context and concept - curatorial
traditions and legal issues colouring terminology.

I will gladly take part in these areas!
a "wordbook" of system terminology acn be useful for
interoperability.

=========================
hans rengman

• META - Kunskap om kunskap                      Hans Rengman  *
  '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
• www.meta.se <http://www.meta.se                                />
  hans@meta.se  *

•                                                           *
  

• Hovslagaregatan 11            tel:  +46 (0)522 - 51 10 94  *
• SE-451 44 Uddevalla                                          *
• Sweden                        GSM:  +46 (0)70 - 718 23 25  *
  ***********  P  Please consider the environment before printing this e-mail