Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes are need to the METS Header default configuration #286

Closed
4 tasks done
jmaferreira opened this issue May 10, 2017 · 3 comments
Closed
4 tasks done

Changes are need to the METS Header default configuration #286

jmaferreira opened this issue May 10, 2017 · 3 comments

Comments

@jmaferreira
Copy link
Member

jmaferreira commented May 10, 2017

  • The "Transfer type" is unnecessary in the form, it has a constant value in SIP 4: "STRUKTURÁLATLAN”.
  • The ’ Transfer specification document’ is the same, it has a constant value in SIP 4: „34/2016. (XI. 30.) EMMI rendelet az elektronikus formában tárolt iratok közlevéltári átvételének eljárásrendjéről és műszaki követelményeiről”
  • ‘Data system name’ and ‘Data system version’ are not mandatory for SIP4
  • ’Package creator software’ and its version are constant values with Roda-in actual version data. Remove them from the form as they are filled automatically by the export procedure.
@jmaferreira jmaferreira added this to the 2.1.0-beta2 milestone May 10, 2017
chalkos added a commit that referenced this issue May 10, 2017
… sure to always add it to the mets header with the specified constant value
chalkos added a commit that referenced this issue May 10, 2017
…t field and making sure to always add it to the mets header with the specified constant value
@chalkos
Copy link
Contributor

chalkos commented May 10, 2017

Regarding part 4, per the Hungarian SIP 4 spec the agent name should be the software name and the agent note should contain the software version. RODA-in writes the software name and version to agent name. ie:

current:

<agent ROLE="CREATOR" TYPE="OTHER" OTHERTYPE="SOFTWARE">
    <name>RODA-in 2.1.0-beta.1</name>
</agent>

SIP 4 spec:

<agent ROLE="CREATOR" TYPE="OTHER" OTHERTYPE="SOFTWARE">
    <name>RODA-in</name>
    <note>2.1.0-beta.1</note>
</agent>

@jmaferreira Should I change the RODA-in export procedure to use name and note?
(and @hsilva-keep let me know if you think this change will break something else)

chalkos added a commit that referenced this issue May 10, 2017
…nd letting RODA-in add that information during the export procedure
@jmaferreira
Copy link
Member Author

jmaferreira commented May 10, 2017 via email

chalkos added a commit that referenced this issue May 10, 2017
…t field and making sure to always add it to the mets header with the specified constant value
chalkos added a commit that referenced this issue May 10, 2017
…nd letting RODA-in add that information during the export procedure
@chalkos
Copy link
Contributor

chalkos commented May 11, 2017

@hsilva-keep is handling the <agent ROLE="CREATOR" TYPE="OTHER" OTHERTYPE="SOFTWARE"> part

hsilva-keep added a commit that referenced this issue May 11, 2017
…om the others (name in the name element, and version in the note element; as opposite to the others where name & version go to the name element; #286)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants