New Testament Virtual Manuscript Room
  1. New Testament Virtual Manuscript Room
  2. NTVMR-61

Don't clear folio numbers that have been manually entered

    Details

    • Type: Bug Bug
    • Status: Open (View Workflow)
    • Priority: Major Major
    • Resolution: Unresolved
    • Labels:
      None

      Description

      Currently the "Clear Folio Numbers for this Doc" option does exactly that, including clearing all manually entered folio numbers. Folio numbers are very helpful when working with our transcriptions (Rachel dislikes using the VMR when folio numbers are not present). They take a long time to manually add, so it is very aggravating when they are cleared. Can this option be changed so that it only clears imported folio numbers, and does not clear those that have been manually added?

        Activity

        Hide
        Troy A Griffitts added a comment -

        Related issue NTVMR-41

        The reason we can remove indexing data that has been automatically added from a transcription is that our index data table has a USERID column and for auto-generated index information we store 'ECM' as the USERID, so it's easy to remove all those rows for the document.

        When it comes to folio numbers, this is just a data field on the Document Page record. It isn't its own row in the database
        so we don't have anything like a USERID that specifically tells us who entered data for that field.

        We can probably come up with a hack by adding a private column to the table, next to the FOLIONUMBER column.. something like: FOLIONUMBERGENERATED as boolean.
        We could set this whenever we auto-generate the number. That would let us know if the number was generated or not and then we could know which ones to delete.

        Show
        Troy A Griffitts added a comment - Related issue NTVMR-41 The reason we can remove indexing data that has been automatically added from a transcription is that our index data table has a USERID column and for auto-generated index information we store 'ECM' as the USERID, so it's easy to remove all those rows for the document. When it comes to folio numbers, this is just a data field on the Document Page record. It isn't its own row in the database so we don't have anything like a USERID that specifically tells us who entered data for that field. We can probably come up with a hack by adding a private column to the table, next to the FOLIONUMBER column.. something like: FOLIONUMBERGENERATED as boolean. We could set this whenever we auto-generate the number. That would let us know if the number was generated or not and then we could know which ones to delete.
        Hide
        Bruce Morrill added a comment -

        Sorry for the difficulty! But the folio numbers are very useful when working with transcriptions which reference them. And it is discouraging adding folio numbers to the VMR when we know they can be easily erased in one click.

        Show
        Bruce Morrill added a comment - Sorry for the difficulty! But the folio numbers are very useful when working with transcriptions which reference them. And it is discouraging adding folio numbers to the VMR when we know they can be easily erased in one click.

          People

          • Assignee:
            Troy A Griffitts
            Reporter:
            Bruce Morrill
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: