Hi friends,
I have a suggestion about the import of archetypes by RDF from other platforms. Could it be possible that, even working with data in Spanish, this import could only be via English? Because it is generating a lot of human errors, as we normaly forget to change the language of the data for doing it and we are importing archetypes in a masive way. The principal problem is that we generate duplicities and that we have to change all the contents from one language to another "by hand".
If you manage to achieve it, it could be really usefull for us.
Thank you!!

Hi Elena

I have tried to import an Ocre RDF with a Spanish installation and the languages are imported correctly (the tool respect the language of the data correctly), could you put an example of the problem? (something as: importing http://numismatics.org/ocre/id/ric.1(2).aug.1A the field Material (numisdata32) only import the English lang...)

Best

Hi Alex,
I think I haven't explain myslef properly before.
The field "Diseño anverso" and "Diseño reverso" are directly copied in English (as they don't have translation) from OCRE or CRRO.
When we work (by mistake or because we are managing a lot of information and our team is getting bigger and bigger) with the data in Spanish, the import goes rightly there although is in English. So, we have to open the multilanguage tool, cut the data imported in the place for the translation in Spanish and pasted it to the English field.
It also happens sometimes with the names of the emperors, when they don't have translation in Spanish (as Vespasian, that should be Vespasiano), the data goes directly to Castillian although is in English. It generates a lot of secundary problems as, for example: the name of the mints or the emperors, I have to respect them in English because if I translate them when I do another import it will duplicate the data as the names doesn't match.
I have comment it with Manuel and we think that the problem would be resolved if the data with no traslation to import goes to English, but of course, maybe there is another way to skip this problem.
Other thing is the field "clave" I think it should be NOLAN, as it is a code normally generated by the abbreviation of the catalogue you are using, translating it does not seem to have a point for me.
Thank you!!!

  • Alex replied to this.

    Hi Elena

    Ok, I understand the issue: When the RDF do not include lang for own data, you will need to specify what is the "default" lang of the RDF and it could match not with the Dédalo installation default lang.
    The RDF asume that his own data is in English but your Dédalo installation asume that default data is in Spanish.
    ...and you know, that you can change the lang before import, but, sometimes you or your team forget do this change...

    Ok, let me think about this, because the RDF import tool is not only for Nomisma RDFs and it's not only for English world. Maybe, a solution could be add a Lang control inside the import tool. So, when you click the import you will see the default lang and choose if you want import in English, Spanish, Arab... etc.

    I will back with a "proposal".

    For the "Key" field (numisdata81) inside Type?, will need more quorum to do this change... @Manuel Gozalbes, @Pere Pau, @Markus, What do you think about that?

    Best

    Hi
    After our experience with MIB, the "Key" field (numisdata 81) needs some kind of translation. When creating a typological catalogue this field allows to explain the basic features of the type, since is not always clear after the standard description fields (legend or design).
    For instance, it's useful for indications like:

    • Type 13a) regular sign, 13b) inverted sign. This heading facilitates cataloguing
    • Type 4) Three locks behind the ear. Type 5) Two locks behind the ear. This difference is not explained in the design (i.e. Head to the right).
      In these cases translation seems to be neccessary, I think...
      Best
    6 days later

    Hi,
    I am a bit confused because i think two seperate things are discussed here and i am not sure what exactly you want to change for the "key" field. I think i need more information to offer my opinion. Sorry.

    • Alex replied to this.

      Hi

      elena ...we think that the problem would be resolved if the data with no traslation to import goes to English, but of course, maybe there is another way to skip this problem.

      I change the import to show the language than you can chose to use as default import data when the RDF do not specify the lang for data.

      Update your installation to the latest v5.9.1 and update the ontology you can update both in admin tool, the ontology need to be: Dédalo 12-10-2022 12:10 Benimamet or more recent.

      I hope that this solution can help to import RDF data in a correct way.

      Note: keep in mind that if you change the language inside the tool you are changing Dédalo data lang... if you want back to default lang you will need to change it in the menu.

      Markus I think i need more information to offer my opinion.

      Elena has proposal to change the field key (numisdata81) inside types, to be not translatable, this field:

      @elena maybe @Markus has right, I think is better open separate threads for every topic, it could be confusing... try to separate each thematic for next questions / debates / topics... 😉

      Best

          Thank you for the changes at the RDF Alex! We surely will improve our work with that.
          Sorry for mixing the "key" topic in here, nevertheless, reading Manuel argument I think he is right and we have to leave it like it is.

          Thanks to both!

          DÉDALO AGORA. MANAGING CULTURAL HERITAGE ARCHIVES - dedalo.dev