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

Move and rename 033 #674

Closed
HirschSt opened this issue Aug 28, 2018 · 9 comments
Closed

Move and rename 033 #674

HirschSt opened this issue Aug 28, 2018 · 9 comments

Comments

@HirschSt
Copy link
Contributor

this should be directly above 518 and renamed from "date".
Keep in mind: 033 is part of the material group, 518 not, so it's tricky to prevent data corruption.

@lpugin
Copy link
Contributor

lpugin commented Aug 28, 2018

I think the decision was to remove 033 completely. We need to investigate this

@HirschSt
Copy link
Contributor Author

I'm not sure if removing was RISM-CH related, probably @jenniferward knows more.

@jenniferward
Copy link
Contributor

033 came from CH, it was never in Kallisto.
According to my notes, "Stephan wants to keep the field in case we import data with it." (23. Nov. 2016)

If we keep it, it should be called "Coded date for performance" in English and placed below the 518.

@cgueggi
Copy link
Contributor

cgueggi commented Dec 4, 2018

Since we still have this field, I'd propose to rename it as Jennifer called it "Coded date for performance" and replace it to the "references and notes" section (above 518). It doesn't make any sense to have it in the material description. Would this be possible for Muscat 5.1 (or even 5.0.1)?

@jenniferward
Copy link
Contributor

jenniferward commented Apr 10, 2019

What is the status of this? Can it, as an initial step at least, be moved to be above the 518? Having it so close to the 260 leads to mistakes.

Edit: Actually I think this order makes more sense:
518
033
651
That way it makes more sense from a cataloger's point of view: the note gets put in the 518 as free text and the standardized/coded forms get put in the fields that follow.

@cgueggi
Copy link
Contributor

cgueggi commented Apr 10, 2019

I'm ok with the proposal of @jenniferward
I just think it's important to take it out of the material description

@xhero xhero added this to Working on this week in Muscat 6.1 via automation Feb 18, 2020
@xhero xhero added this to the 6.1 milestone Feb 18, 2020
@xhero
Copy link
Contributor

xhero commented Feb 19, 2020

Plan:

  • 6.1 remove from editor
  • 6.2 remove altogether

@xhero xhero removed this from Working on this week in Muscat 6.1 Feb 19, 2020
@xhero xhero modified the milestones: 6.1, 6.2 Feb 19, 2020
@xhero xhero added this to To do in Muscat 6.2 via automation Mar 11, 2020
@xhero
Copy link
Contributor

xhero commented Mar 18, 2020

Make a list with the date values, used to fix the data.

@xhero xhero moved this from To do to In progress in Muscat 6.2 Apr 8, 2020
@xhero xhero modified the milestones: 6.2, 6.3 Apr 22, 2020
@xhero xhero removed this from In progress in Muscat 6.2 Apr 22, 2020
@xhero xhero added this to To do in Muscat 6.3 via automation Apr 22, 2020
@xhero
Copy link
Contributor

xhero commented Apr 22, 2020

List il done, cleanup script will be run after 6.2 release

@xhero xhero removed this from To do in Muscat 6.3 Jul 8, 2020
@xhero xhero added this to To do in Muscat 7.0 via automation Jul 8, 2020
@xhero xhero closed this as completed Aug 25, 2020
Muscat 7.0 automation moved this from To do to Done Aug 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Muscat 7.0
  
Done
Development

No branches or pull requests

5 participants