Note types

[Tim Hutchinson]

Hi,

I could be missing something obvious here, but I'm wondering where (or
if) the Note type taxonomy is used, e.g. in data entry templates.

E.g. Display note, Maintenance note, etc.
I thought there might be something in the control area but I don't see
anything. There is an "archivist's note" but this doesn't appear to be
linked to the "archivist's notes" field in the ISAD template (based on
the different spelling).

This comes up in the context of issue 643 -
http://code.google.com/p/qubit-toolkit/issues/detail?id=643
which says that <physloc> should be imported using the logic "if
<physloc> is given without a <container> element, set a note with type
'location'." Does this refer to something else?

Thanks
Tim

--

Tim Hutchinson
University of Saskatchewan Archives
301 Main Library, 3 Campus Drive
Saskatoon, SK S7N 5A4
tel: (306) 966-6028
fax: (306) 966-6040
e-mail: tim.hut...@usask.ca
web: http://www.usask.ca/archives/

[Jesús García Crespo]

Hi Tim,

On Wed, Mar 30, 2011 at 10:41 PM, Tim Hutchinson <tim.hut...@usask.ca> wrote:

I could be missing something obvious here, but I'm wondering where (or if) the Note type taxonomy is used, e.g. in data entry templates.

E.g. Display note, Maintenance note, etc.
I thought there might be something in the control area but I don't see anything. There is an "archivist's note" but this doesn't appear to be linked to the "archivist's notes" field in the ISAD template (based on the different spelling).

I am not sure if I understand what you mean, but users can't choose the type of note from the forms. Notes are a database entity used in different places in the application, but each use has its own type assigned. All these types are grouped in the taxonomy "Note types".

 

This comes up in the context of issue 643 - http://code.google.com/p/qubit-toolkit/issues/detail?id=643
which says that <physloc> should be imported using the logic "if <physloc> is given without a <container> element, set a note with type
'location'." Does this refer to something else?

As far as I know, "location" is a type of physical object. In my opinion, it does not make sense to assign this type to a note, because it is not part of "Note types" taxonomy. But I think that one of my teammates could give you a better response. I guess that a new type also called "location" should be created, but under "Note types" taxonomy.

Regards,

--
Jesús García Crespo

[Tim Hutchinson]

Hi Jesús,

Thanks for the explanation. So if understand you correctly, additions to the note types taxonomy would require other changes to the application? - as opposed to, for example, the RAD notes taxonomy where a new term in that taxonomy results in another option in the pull-down list.

There are certainly cases where recording a location independent of a container makes sense, and this may be a matter for further development/discussion. In EAD, <physloc> and <container> are independent (not nested) - which presumably is what led to the wording of issue 643. One example would be a note indicating that a collection is off-site and needs to be requested in advance. And for example our provincial archives has offices in two different cities, so they use a note to indicate which office has the records.

Tim

[Jesús García Crespo]

Hi Tim,

2011/4/1 Tim Hutchinson <tim.hut...@usask.ca>

Thanks for the explanation. So if understand you correctly, additions to the note types taxonomy would require other changes to the application? - as opposed to, for example, the RAD notes taxonomy where a new term in that taxonomy results in another option in the pull-down list.

Actually, you can add a new term to note types taxonomy manually. But if you want to add a new funcionality in ICA-AtoM, this new term should be included as part of it in the default ICA-AtoM data set. That's why other note types are protected (non-editable by users), their values are used in the application logic.

Adding a new term is very easy using the Symfony fixtures system. However, you have to take care of users who come from older versions. Your new term must be included as part of the migration script to make sure that migrated data sets are fully compatible with new application features.

 

There are certainly cases where recording a location independent of a container makes sense, and this may be a matter for further development/discussion. In EAD, <physloc> and <container> are independent (not nested) - which presumably is what led to the wording of issue 643. One example would be a note indicating that a collection is off-site and needs to be requested in advance. And for example our provincial archives has offices in two different cities, so they use a note to indicate which office has the records.

I see what you mean. We are going to create a new page in our wiki to document how to create new taxonomies (regarding to this discussion thread), I'll make sure that this point is also described.

Thank you!

--
Jesús García Crespo,
Software Engineer, Artefactual Systems Inc.
http://www.artefactual.com | +1.604.527.2056