In Content Types - utilize Link field type instead of Text for URLs

[dmoses]

Improvement.
If we are storing URLs in our content types it makes sense to me to leverage the Link module. It'll help validate URLs and will also turn our currently static text links into links that are clickable.

• Fedora Path
• fedora:hasParent
• PCDM:HASMEMBER

dm

[ruebot]

I like where this is going @dmoses!

[dmoses]

@DiegoPino I think this is tied to #106.

For fields that are relationships ... should they be defined with a field type of Entity Reference ?
Would those relationships only need to reside in the Collection content type? Or would they also need to be expressed in the objects referenced?

[DiegoPino]

@dmoses great question: so you mean adding https://www.drupal.org/project/entityreference to the mix. In my opinion, the fedora ones should be pointing to url (since they are external, not internal entities really) and then the question arises if pcdm:hasMember could be an internal entity reference, that is mapped to an fedora resource path on update/sync (last one mapped back) or we will also keep there the fedora url and use a different semantic layer (other properties) for managing our drupal relations. The fedora ones are tied to any fedora/islandora object. the pcdm:hasMember is an pcdm:collection to pcdm:object relation, but it really depends on how you interpret the pcdm ontology, since it's RDFs, lots of space for "interpretation"

I would really love to have this conversation ASAP, since i'm planning/coding to move all fedora semantic into entity properties instead of bundled extra fields as part of #106 . Makes no sense to allow users to mess around with those, more over, since we are not exposing them (localhost:8080/fedora… makes also no sense as public linked data).

@Islandora-CLAW/7-x-2-x-sprinters, what are your ideas on this?

[sprklinginfo]

@DiegoPino++ if we are moving toward custom entities for all fedora objects in Drupal, I feel it does make sense that all fedora semantic related stuff should be entity properties, bundled extra fields should be used to extend for different content types, e.g. simple image, book, video...etc.

[sprklinginfo]

@dmoses agreed to display links if a field contains url. But we also have to consider whether we display those fedora links to end user which may look like messy and scary. We have discussed a little bit on #84 whether we should hide those to end users, but admin/manager still can access from "manage" view.

[dannylamb]

Closing D7 issues. Entity references will be widely used in D8