Scope out basic extent of functionality about csvimport HOT 2 CLOSED

Things we're accepting as values from the CSV:

• values for any property
  • literals
  • literal URIs
  • internal URIs???
    • to existing resources (already in Omeka, so they have an ID)
    • to resources within the same file (no ID exists yet) (questionable)
  • other data types? some might be appropriate, but others not? (controlled vocab?)
• other basic resource information
  • member of item set(s)
    • by existing ID
    • by common name in the CSV? (always creates new ones)
  • publicness
  • resource class (by ID?, QName?, some weird combo of vocab label and class label)
  • resource template (by label, or ID)?
  • ownership??? (restricted by role, specified by email?)
• simple media (one column only, no other data)???
• other random X (added by module)?
  • e.g., Mapping location

Things you can set in bulk, for the whole file:
(choosing any would lock out doing them on a row-by-row basis)

• other basic resource information
  • member of item set(s)
    • by existing ID
    • by common name in the CSV? (always creates new ones)
  • publicness
  • resource class (by ID?, QName?, some weird combo of vocab label and class label)
  • resource template (by label, or ID)?
  • ownership??? (restricted by role)
• module-added stuff??

Types of resources we support (as first-class)?

• Items
• Media (interleaved?) (seperately, but requires existing item ID column)
• Item Sets (separately?, interleaved?)
• allow subsequent imports

from csvimport.

• Undo
• Stop

from csvimport.