2.x for 1.x users - work in progress #97
Conversation
|
@Islandora-Labs/7-x-2-x-sprinters please review and provide feedback when you can. |
| * Fill out a metadata form | ||
| * Upload object/Ingest | ||
|
|
||
| In Fedora 3: |
There was a problem hiding this comment.
This should probably be Fedora 4, right?
There was a problem hiding this comment.
If you want to get technical, sure. /me goes off to fix that.
|
Great start! I think the outline is spot on and the text that is there is at the right reading level. Isn't there a Fedora4 document that describes the differences between Fedora3 and Fedora4? I think this would be a good place to link it in. The linking to the The Fedora 4 object model would also be useful. We should also refer people to the Fedora 3 to 4 Upgration document where they can get an overview of that process. We don't need to talk about it deeply here -- just a reference so people can go to find more information if desired at this stage. |
|
There's this from Fedora 4: https://wiki.duraspace.org/display/FEDORA4x/Concept+Mapping+-+Fedora+3+to+4 Very handy. Will include a link to it (and am borrowing from it heavily!) |
|
@dltj there is a lot of upgration documentation in the migration section. |
|
bump @Islandora-CLAW/7-x-2-x-sprinters (waiting for everybody accept invites to new GitHub org team) @whikloj ...@manez can you also add @nigelgbanks to the sprinters team? I just noticed he signed up for the sprint. Since I'm no longer an owner, I can't do that. I forgot to make myself a team admin before we did the ownership shifts 😢 |
Rolling in some of @rosiel's notes
spelling counts
| * `Non-RDF Source`: Roughly equivalent to a datastream. A Non-RDF Source (or binary) is simply a bitstream (e.g. JPG, PDF, MP3, etc.). | ||
|
|
||
| ###Datastreams | ||
| In Islandora 7.x-2.x, RDF datastreams (RELS-EXT and RELS-INT) are stored as pure RDF in Fedora. Binary datastreams (files, images) are `Files` (see [PCDM]()). Metadata datastreams (MODS, DC, DwC, PBCore, etc) are whatever you want them to be: either binary files of XML, or mapped to your choice of RDF. |
There was a problem hiding this comment.
Files are technically called nonRdfResources... but do we want to further confuse people here.
What do you think @daniel-dgi?
|
ok, I think it's ready for merge now. It could certainly stand for some expansion if others want to add to it, but for a starter document, at least all of the holes are filled in. |
|
@manez I shall review again! @Islandora-CLAW/7-x-2-x-sprinters please review and provide feedback. |
|
@manez still need to address this https://github.com/Islandora-CLAW/CLAW/pull/97/files#r44413981 |
|
Reviewing ... a small edit here: Object Structure |
| ####PIDs | ||
| Every object in a Fedora 3 repository had a Persistent Identifier following the pattern `namespace:pid`. Fedora 4 resources do not have PIDs. Instead, since Fedora 4 is an LDP server, their identifiers are fundamentally their URIs. The PIDs of objects migrated from a Fedora 3 repository can still be stored in Fedora 4, as additional properties on the new Fedora 4 resource. | ||
|
|
||
| Since resources are stored as `nodes` on the Drupal side of Islandora 7.x-2.x, they also have Drupal uuids. |
There was a problem hiding this comment.
I would capitalize uuid > UUID.
| ###Collections | ||
| Because objects in Fedora 3 were stored in a flat graph structure instead of a hierarchy, what were presented as collection in Islandora 7.x-1.x were actually objects on the same level as their child objects, with the 'container' or 'folder' aspect of them being a fiction for display created by the relationships between the objects. In Fedora 4, resources do have a true hierarchical structure and must have a `fedora:hasParent` relationship to know where they belong in a given repository. Indeed, to migrate objects over from Fedora 3 to Fedora 4, parents must arrive before their children. | ||
|
|
||
| In its current incarnation, Islandora 7.x-2.x does not include a default display for collections. Instead, Drupal Views can be used to build collections around the `pcdm:hasMember` value. For more information, please see [How To Create A Collection View](user-documentation/editing-basic-image-form-in-islandora-7.x-2.x.md). |
There was a problem hiding this comment.
I don't think the link is correct for "How to Create a Collection View" ... I have the documentation started, but I'm stumped on how to create a Drupal view that allows you to display a collection of nodes that don't themselves have some sort of information that tells you its parent node.
There was a problem hiding this comment.
You're correct. I put a placeholder in for when there is documentation for that - it should not be linking to editing forms.
|
Updated based on feedback - hopefully more accurate now. |
|
|
||
| ###Collections | ||
| Because objects in Fedora 3 were stored in a flat graph structure instead of a hierarchy, what were presented as collection in Islandora 7.x-1.x were actually objects on the same level as their child objects, with the 'container' or 'folder' aspect of them being a fiction for display created by the relationships between the objects. In Fedora 4, resources do have a true hierarchical structure and must have a `fedora:hasParent` relationship to know where they belong in a given repository. Indeed, to migrate objects over from Fedora 3 to Fedora 4, parents must arrive before their children. In its current incarnation, all objects in a 7.x-2.x repository have the Fedora root as a parent and relationships are managed via a ```pcdm:hasMember``` triple | ||
|
|
There was a problem hiding this comment.
predicate, not triple. Need a full stop too.
...also via the, not via a.
and you only need to wrap pcdm:hasMember is a single back-tick, not three.
|
I'm a 👍 here. Thanks @manez @Islandora-CLAW/7-x-2-x-sprinters one final look before we merge? |
|
Great work! Thank you @manez 👍 |
|
Looks good. @manez 👍 |
|
Merging this since we've had time for comment, and sprint is over. |
2.x for 1.x users - work in progress
for Issue #71