Value list for agents

[karinbredenberg]

There is a need to add contact_person as a type of agent.

[karinbredenberg]

The suggestion is:

Addition of value contact_person in the agentType attribute. Update made in both XSD and specification.

Board members acknowledgment of the issue: Tick the box in front of you name to indicate that you have looked at the suggestion.

• [x] Karin Bredenberg (Kommunalförbundet Sydarkivera, chair)
• [x] Anders Bo Nielsen (National Archives of Denmark)
• [ ] Anja Paulič (National Archives of Slovenia)
• [ ] Arne-Kristian Groven (National Archives of Norway)
• [ ] Gregor Zavrsnik (Geoarh)
• [ ] Janet Anderson (Highbury Research & Development Ltd.)
• [x] Maya Bangerter (Swiss Federal Archives)
• [x] Miguel Ferreira (KEEP Solutions)
• [x] Stephen Mackey (Penwern Limited)
• [x] Sven Schlarb (Austrian Institute of Technology)

Voting (Decision making will be carried out on the basis of majority voting by all eligible members of the Board. In the case of a tied vote, decisions will be made at the discretion of the Chair)

Tick the box in front of you name to say yes to the suggestion.

• [x] Karin Bredenberg (Kommunalförbundet Sydarkivera, chair)
• [ ] Anders Bo Nielsen (National Archives of Denmark)
• [ ] Anja Paulič (National Archives of Slovenia)
• [ ] Arne-Kristian Groven (National Archives of Norway)
• [ ] Gregor Zavrsnik (Geoarh)
• [ ] Janet Anderson (Highbury Research & Development Ltd.)
• [x] Maya Bangerter (Swiss Federal Archives)
• [ ] Miguel Ferreira (KEEP Solutions)
• [x] Stephen Mackey (Penwern Limited)
• [x] Sven Schlarb (Austrian Institute of Technology)

[jmaferreira]

Hi,

What is the intended use of the new value contact_person? What sort of contact should it represent?

Current values already include quite a large list of options:

• administrator
• agent
• archiver
• authorising_person
• borrower
• counterpart
• creator
• custodian
• deliverer
• dispatcher
• editor
• ipp_owner
• main_signatory
• mover
• opening_person
• other_signatory
• owner
• reader
• recipient
• receiver
• relocator
• responsible_person
• sender
• user
• other

[karinbredenberg]

The contact_person is coming as input from a use case where none of the roles present is possible to use, it is a person whom is just acting as the contact. Instead of using other and an other description attribute giving contact person as the value the suggestion was made to add the role to simplify the encoding.

[karinbredenberg]

6 DILCIS Board members have acknowledge the issue 4 DILCIS Board members agree with the solution

The update will be published 17th of May 2024.