Uploaded image for project: 'VIVO'
  1. VIVO
  2. VIVO-637

Various date/time value properties not configured with list views

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: v1.6
    • Component/s: Custom forms
    • Labels:
      None
    • Attachments:
      0
    • Comments:
      0

      Description

      The properties vivo:dateFiled, vivo:dateIssued, vivo:expirationDate, vivo:dateTime, and <http://purl.org/spar/c4o/hasGlobalCountDate>.

      The property labeled "publication date" is a faux property of vivo:dateTimeValue – I'm thinking these can't be since they have different semantic meaning, and multiple dates need to be stored with patents.

      Before my last deployment, I had added the vitro:customEntryFormAnnot "edu.cornell.mannlib.vitro.webapp.edit.n3editing.configuration.generators.DateTimeValueFormGenerator"^^xsd:string to each of these properties, and they come up with the form, but appear in the back end to have been saved as statements of the property http://vivoweb.org/ontology/core#dateTimeValue – not sure whether this is an issue with the form or the list view.

      I'm also not sure whether or where vivo:dateTime is used.

        Attachments

          Activity

            People

            • Assignee:
              tlw72 Tim Worrall
              Reporter:
              jc55 Jon Corson-Rikert
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: