Merge branch 'virtual_collections' of mikesname/ehri-rest into virtual_collections
WP2EadImporter imports the eads, and simultaneously creates a virtual collection pointing to all the relevant descriptions, and links between the description, authoritativeRecords and the VirtualUnit
Merge branch 'master' of mikesname/ehri-rest into virtual_collections
the virtual-import command takes a 'virtualcollection' argument into which the virtualunits will be imported
working out how to import eads as virtualunits
merged with mikes, VirtualUnits are now DescribedEntities, so an EAD file can be imported as a virtual collection consisting solely of VirtualUnits
command created to import a EAD file as a completely virtual structure. no docUnits are created
first attempt to create the virtual collection from a separate EAD. structural links between virtual nodes are all to root, should be their direct parent.
merged with master
bundesarchive does not need a special import anymore. furthermore, the properties file has been changed so it can take an attribute with value to choose the right tag, see bundesarchive.properties for an example.
maintenance from the EAD is added as MaintenanceEvents to the topLevel DocumentsDescriptions
VC's should be done in a different way. Through the portal?
added the stadsarchief. some cleanup of unused importers/tests
changing the way the vc are imported
wp2 stuff as normal imports, using ead-import and their own properties file.
value of author-tag in ead added to every documentsDescription. EAD's cannot be imported into a virtual collection. It will be possible to import them AS VirtualUnits, though, which can link to actual Units.
virtual collections as 'skeleton' virtualunit-trees can be imported from a EAD file. The repository/unit combo's referred to should be already in the graph.