Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    xhero
    @xhero
    but I’m a bit unsure, Muscat is very marc-centered
    Andrew Hankinson
    @ahankinson
    Yeah... there's just a lot of things that I'm looking at that (I think) are pretty important to keep around, but there's no real pigeon hole to put them in.
    Like the former DIAMM source number so that we can translate between the old database source numbers and the new ones.
    xhero
    @xhero
    yeah I understand
    we need to talk togeather with Laurent for this, we could expand the model if necessary
    Andrew Hankinson
    @ahankinson
    Are the input forms controlled on a MARC-field basis? Or can they go directly to a model field?
    xhero
    @xhero
    in the marc models all editing goes directly to marc
    the model fields are caches of the most used values in marc that get updated after saving
    Andrew Hankinson
    @ahankinson
    So MARC -> model fields
    Is there model fields -> MARC?
    xhero
    @xhero
    no
    Andrew Hankinson
    @ahankinson
    hrm
    xhero
    @xhero
    well, not really
    there are some relations that update marc from the fields
    for example in the linked fields with $0
    Andrew Hankinson
    @ahankinson
    Right, but the storage is essentially MARC
    for sources at least
    xhero
    @xhero
    yes
    Andrew Hankinson
    @ahankinson
    That's unfortunate
    xhero
    @xhero
    well it is the design of muscat to store data as marc
    Andrew Hankinson
    @ahankinson
    Yeah, it just seems like that's also a limitation that restricts the ability to expand it further
    BTW, I'm not trying to be critical... just trying to figure out a way to make it do the things we need it to! :)
    It would be unfortunate to launch a new DIAMM that's only capable of exposing a subset of the information we currently have
    It would be nice if the MARC was just another serialization format...
    xhero
    @xhero
    well I do understand :)
    it is just that on how Muscat is designed now it is not a straightforward thing to implement
    not that it cannot be done
    Laurent Pugin
    @lpugin
    For linebreaks I would suggest to split them into repeated field. I would expect them to be wanted in note fields. Instead of a line-break, you can create another note field. Would this work?
    xhero
    @xhero
    we could also render this for MARC. We had it for psmd
    Andrew Hankinson
    @ahankinson
    PSMD?
    Laurent Pugin
    @lpugin
    You mean <p>? Or \n?
    xhero
    @xhero
    Printed Sacred Music Database ;)
    Andrew Hankinson
    @ahankinson
    Yeah, I was thinking of doing it in a related field, but I couldn't find any best practices
    xhero
    @xhero
    I think we converted \n to <p> or <br>
    Laurent Pugin
    @lpugin
    @xhero all this was a bad idea
    You can just repeat the field
    Andrew Hankinson
    @ahankinson
    oops... repeated field
    not related
    Laurent Pugin
    @lpugin
    ok
    xhero
    @xhero
    repeating is good for me, much better than having unsave strings in views
    Laurent Pugin
    @lpugin
    I think it would be a good practice
    xhero
    @xhero
    (BTW unrelated: muscat seems to work well in debian 8.2 with rails 2.1)
    Andrew Hankinson
    @ahankinson
    We do have some tricky data stored in the description, usually from bad copy/paste jobs
    like bullet points
    xhero
    @xhero
    in 2.0 we had all the digital objects stuff which was quite over the top
    but you could basically relate any data (text, images, etc) arbitrarily to a source
    if this stuff does not realle belong to marc could we have something similar?
    *really
    Andrew Hankinson
    @ahankinson
    Well, the best thing would be to make MARC an input/output format, and store the stuff internally as something else
    that way we could support things like METS, DC, JSON-API