Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Welcome to the CollectiveAccess support forum! Here the developers and community answer questions related to use of the software. Please include the following information in every new issue posted here:

  1. Version of the software that is used, along with browser and version

  2. If the issue pertains to Providence, Pawtucket or both

  3. What steps you’ve taken to try to resolve the issue

  4. Screenshots demonstrating the issue

  5. The relevant sections of your installation profile or configuration including the codes and settings defined for your local elements.


If your question pertains to data import or export, please also include:

  1. Data sample

  2. Your mapping


Answers may be delayed for posts that do not include sufficient information.

Updating the Multipart_ID_numbering idno

Hi,

I am trying to set up a Multipart_ID_mumbering to allow the system to generate the correct idno based on the object's hierarchy. Until now, everything is fine!

But the catalog work is in progress, and the catalogers are foreseeing that there are a lot of objects that will need to be moved to another places in the hierarchy, when they revise the archive.

It is possible (maybe through some development in our part) to allow the idno be "regenerated" when needed? As by now, even with the settings in the multipart_id_numbering.conf only the last element of the generated id is editable. If a document is moved to another fond, for example, the first part of the generated idno must be changed as well.

Below is a copy of the relevant multipart_id_numbering.conf file block:
	ca_objects = {
__default__ = {
separator =,
elements = {
accession_number = {
type = FREE,
width = 30,
editable = 1,
description = _(Accession number)
}
}
},
fonds = {
separator = .,
elements = {
accession_parent = {
type = ALPHANUMERIC,
width = 3,
description = "identificação do fundo",
editable = 1
}
}
},
groups = {
separator = .,
elements = {
accession_parent = {
type = PARENT,
description = _(Accession parent)
},
object_number = {
type = SERIAL,
width = 2,
description = _(Object number),
editable = 1,
sequence_by_type = 1,
table = ca_objects,
field = idno,
sort_field = idno_sort
}
}
},
subgroups = {
separator = .,
elements = {
accession_parent = {
type = PARENT,
description = _(Accession parent)
},
object_number = {
type = SERIAL,
width = 3,
description = _(Object number),
editable = 1,
sequence_by_type = 1,
table = ca_objects,
field = idno,
sort_field = idno_sort
}
}
},
series = {
separator = .,
elements = {
accession_parent = {
type = PARENT,
description = _(Accession parent)
},
object_number = {
type = SERIAL,
width = 4,
description = _(Object number),
editable = 1,
sequence_by_type = 1,
table = ca_objects,
field = idno,
sort_field = idno_sort
}
}
},
file = {
separator = .,
elements = {
accession_parent = {
type = PARENT,
description = _(Accession parent)
},
object_number = {
type = SERIAL,
width = 5,
description = _(Object number),
editable = 1,
sequence_by_type = 1,
zeropad_to_length = 5,
table = ca_objects,
field = idno,
sort_field = idno_sort
}
}
},
documents = {
separator = /,
elements = {
accession_parent = {
type = PARENT,
description = _(Accession parent)
},
object_number = {
type = SERIAL,
width = 7,
description = _(Object number),
editable = 1,
sequence_by_type = 1,
zeropad_to_length = 7,
table = ca_objects,
field = idno,
sort_field = idno_sort
}
}
},
document_parts = {
separator = -,
elements = {
accession_parent = {
type = PARENT,
description = _(Accession parent)
},
object_number = {
type = SERIAL,
width = 4,
description = _(Object number),
editable = 1,
sequence_by_type = 1,
zeropad_to_length = 4,
table = ca_objects,
field = idno,
sort_field = idno_sort
}
}
}
},
Thanks

Comments

  • I'm afraid this isn't possible at the moment. Identifiers are intended to be invariant. It's not typical that they change based upon location. That said, it would be possible to develop a plugin to do this if you really needed it to work this way.
  • All right, I expected that would be the case. 
    We will see the alternatives here and, if necessary, we will develop a plugin for this.

    Thank you!
  • edited November 2017
    Generally speaking, if your identifiers change over time based upon the state of other fields they're not really identifiers. Before you implement this it would be a good idea to consider if changing the identifier is really the right way to go. You might simply make another field (or a display template) that encodes this information.
Sign In or Register to comment.