search

lcnetdev / bfe

Creative Commons Zero v1.0 Universal
61 stars 27 forks source link

3.2.2 Add field to a form not present in a profile #15

Closed kirkhess closed 6 years ago

kirkhess commented 6 years ago

Enable adding new element not in the profile being used, then display

kirkhess commented 6 years ago

Here's a list of properties - we're thinking this might need to be limited to literals:

These BIBFRAME properties can be input as literals:

acquisitionTerms ascensionAndDeclination awards classificationPortion code coordinates copyrightDate count credits custodialHistory date degree dimensions duration edition editionEnumeration editionStatement electronicLocator equinox exclusionGRing firstIssue hierarchicalLevel historyOfWork itemPortion lastIssue legalDate mainTitle musicKey musicOpusNumber musicThematicNumber natureOfContent noteType organization originDate outerGRing part partName partNumber pattern physicalLocation preferredCitation provisionActivityStatement qualifier responsibilityStatement schedulePart seriesEnumeration seriesStatement spanEnd subseriesEnumeration subseriesStatement subtitle table tableSeq temporalCoverage variantType version

These properties can link to existing works or instances, but they can be input as literals too: absorbed absorbedBy accompaniedBy accompanies continuedBy continuedInPartBy continues continuesInPart dataSource derivativeOf expressionOf findingAid findingAidOf hasDerivative hasEquivalent hasExpression hasInstance hasItem hasPart hasReproduction hasSeries hasSubseries index indexOf instanceOf issuedWith mergedToForm mergerOf originalVersion originalVersionOf otherEdition part of precededBy referencedBy references relatedTo replacedBy replacementOf reproductionOf separatedFrom seriesOf splitInto subseriesOf succeededBy supplement supplementTo translation translationOf

These literals are only used on the Admin Metadata menu: changeDate creationDate derivedFrom generationDate

kirkhess commented 6 years ago

@cledvina Here's some specifics we prob need to discuss:

"Not all of the BF vocabulary is available. I wasn’t able to add bf:generation or bf:provisionActivityStatement to any profile. It appears that the drop-down list is populated with fields from all existing profiles. I don’t think that’s going to work, especially since it’s pulling properties and classes from specialized menus and unrelated profiles. The existing P&P profile is a mess and shouldn’t be used as a source. Any of the fields from the Authorities profiles should be excluded too."

I think the P&P and the Authority issues are kind of oos since ignoring those will fix this - I will take a stab at that prob.

What I think is in scope - because bf:provisionActivityStatement isn't in a profile, you can't pick it from the list of properties in resource templates (if that makes sense). I'm not sure how to fix that -the only thing that came to mind was a crude solution: a profile will one resource template with all the literal properties (see my list above).

A second related issue, if you pick a property which defines some structure, you should actually get the button w/ a modal window not a literal value. That seems to be something you'd want powered by the existing profiles.

kirkhess commented 6 years ago

Existing profiles you can't actually add a property. It only works on a new description.