Skip to content

crossref workflow improvements #6294

@ilippert

Description

@ilippert

For quite a number of my book entries I hold files for the complete book (parent entry). Now, many of these books are edited volumes.

I note 2 small improvements:

  • allow to use the context menu/right click onto the parent entry for generating a new entry that crossreferences the selected parent entry (considering design discussion at UI: maintable: right-click menu: reorder items #6099)
  • and whilst the crossreferencing already well uses many of the fields from the parent entry, several relevant fields are not used (yet):
    • The file/link fields should be crossreferenced, too, as to link to the parent's files/links.
    • The user should be able to flag user defined fields as shown in the crossreferenced entries (I can think of, say, the Printed field for a collection entry, or a field that specify the physical location at which a book can be found)
  • Add option to make content of certain fields inheritable from parent to child entry
  • Improve UI of entry table to account for crossref parent and child entries (see screenshot in this comment)

Together with #5484, #6404, #7057, these improvements would very much ease the use of/work with crossreferenced entries.

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    Free to take

    Status

    High priority

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions