Menu

#13 Add ability to define metadata field names through settings.

open
guy
None
low
2019-03-25
2019-03-21
No

A lot of folks in the cultural heritage community use Guymager (mostly through Bitcurator) and love it. There was thread on twitter today about how it would be great to be able to modify some of the metadata field names for metadata that is captured in guymager.
Ideally I think being able to chose what names to use for the fields through a settings menu would be great, also to be able to define our own field names. Alternatively the options suggested in that twitter field could work:

  1. Evidence number can be changed to “batch number” “accession number” or “collection number”
  2. Examiner could be something like "processor" or like with bagit, "contact name"

I'm happy to coral more input from the Bitcurator community or via twitter if useful.

Thank you,

Euan

Discussion

  • guy

    guy - 2019-03-22

    Hello Euan,
    you currently could change the names by creating a new language file. However, I must admit that this might be too complicated for the standard user. Would you like me to create one for you? You could then tell me if it fits your request. If yes, please send me your "translations" for

    • case number
    • description
    • examiner
    • evidence number
    • notes

    Remark: Please be aware of the fact that those text fields will keep the original labels inside the EWF files . This is due to the fact, that the EWF format does not allow for specifying own labels. Unlike it would be done nowadays (as for example in XML, JSON) the text fields in EWF are simply positional and thus there's no label that could be changed.

    Guy

     

    Last edit: guy 2019-03-22
  • Euan Cochrane

    Euan Cochrane - 2019-03-22

    Thanks Guy!
    I note your point about the EWF files.

    I think I've figured out what needs to be done to create the translation files and where to put them. I may write something up about it, but for now can you confirm this approach is correct (from this twitter thread):
    edit this XML file https://sourceforge.net/p/guymager/code/HEAD/tree/tags/guymager-0.8.8/guymager_en.ts#l26 , compile it with QT_linguist (e.g. https://wiki.qt.io/How_to_create_a_multi_language_application) then put it in /usr/share/guymager as described in /etc/guymager/guymager.cfg and finally edit /etc/guymager/guymager.cfg to change the language variable to be e.g. en2 if your qm file is guymager_en2.qm?

    I found stand-alone qt-linguist GUIs for windows/mac so that is pretty straight forward (see image)

     

    Last edit: Euan Cochrane 2019-03-22
  • Euan Cochrane

    Euan Cochrane - 2019-03-22

    I created a version of the language file here https://yale.box.com/s/ebxgsxxjjl29zdtm0j1crdulhryqn7ei that so far folks on twitter seem happy with.
    Named it guymager_en-CH.qm for "Cultural Heritage".

     
  • Euan Cochrane

    Euan Cochrane - 2019-03-22

    One last update. I wrote up the instructions I followed here and shared them with the folks on twitter.

    Thank you very much Guy!

     
  • guy

    guy - 2019-03-22

    Hehe, looks good! Nice work! If I may just add a small remark: Please do not change /etc/guymager/guymager.cfg directly. Create a new file /etc/guymager/local.cfg and put the line
    Language = en_CH
    into it. The idea behind: If an update is going to be installed, your change would be overwritten if it resides in guymager.cfg.
    As local.cfg is loaded later (see INCLUDE statement at the end of guymager.cfg) the settings residing there overwrite those from earlier configuration files.

    Another remark: It's really nice to see that Guymager is getting used beyond the world of computer forensics. If there's anything else you need for your work just let me know.

    Guy

     
  • Euan Cochrane

    Euan Cochrane - 2019-03-25

    Thanks again. Updated the guide blog post and David added a pull request to BitCurator to make this change https://github.com/BitCurator/bitcurator-distro-salt/pull/2/files. I also passed on your message on twitter.

     

Log in to post a comment.