JSON-LD Import ignore the `list` field

c10n · June 16, 2025, 8:32pm

Version: 1.16.2

When I import JSON-lD (strictly following the export format), the list properties on an item is all ignored despite the items are imported correctly in respect of other fields. The importing behavior respect the drag-and-drop.

This is a snippet of the JSON-LD import file:

    {
      "@type": "Item",
      "template": "https://tropy.org/v1/templates/generic",
      "title": "2. Gap",
      "list": [
        "Encyclopedia",
        "Part 4",
        "G",
      ],

I looked up in the source code, the list is being commented out (6 years ago) might be the cause.

github.com/tropy/tropy

src/common/import.js

494e5b6be


      
          const getNote = (data) => ({
            language: get(data, [tropy.html, 0, '@language']),
            html: get(data, [tropy.html, 0, '@value'])
          })
          
          export function *eachItem(graph) {
            for (let data of graph) {
              yield ({
                data: getMetadata(data, 'item'),
                id: get(data, ['@id', 0]),
                // lists: (data[tropy.list] || []).map(literal),
                photos: flatten(data[tropy.photo]).map(getPhoto),
                tags: (data[tropy.tag] || []).map(n => n['@value']),
                template: get(data, [tropy.template, 0, '@id']),
                type: get(data, ['@type', 0])
              })
          
            }
          }
          
          const props = {

Is it intentional? Is there plan to bring back the feature?

inukshuk · June 17, 2025, 3:16pm

Yes, it’s intentional, but we’ve been exploring ideas how lists could be included in the import. The main reason why we’ve excluded is, is because some projects have specific list structures and e.g., copy pasting items between project windows, you wouldn’t want this to change your list structure. Also, when you import or paste items, you’re importing them into the current list (if you have a list selected), so it would be surprising that the item also gets added to other lists as well. Furthermore, with tags it’s easy to create tags if they are missing, because the tags are defined by their names. But two lists with the same name in different projects are not necessarily the ‘same’ list in the same way tags are.

That said, we could add an import option that includes the lists. The main utility I’d see for this is that it would essentially offer an easy way to duplicate an entire project (basically: select all, copy, and paste into an empty project).

c10n · July 3, 2025, 4:50am

Indeed, my use case here is to modify the structure of list outside Tropy and import them back.