-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Nodes instead of our custom FedoraResource entity #643
Comments
@whikloj We still need to create Content Entities using RDF. So those pulls are still totally relevant. We just need to make them work with Nodes instead. |
I've got this roughly working with nodes and have re-exported the core and collection yaml. When I've got images re-exported i'll issue PRs for all three so people can take a test drive. |
You can totally run through these commands and check everything out, but #649 will need to get resolved before things will flush to Fedora again. Just a heads up. The PRs for this issue are:
Testing Instructions
Wanna get really crazy?
|
Tested and all works as expected. Really great to be able to use generate content to test out now. Nodes open up a really nice world in Drupal that I've been missing for about 10 years now 😄 |
👍 All 3 work as expected. We'll need to consider whether an islandora_image that is saved but not published should be synced to Fedora. |
@ruebot you go ahead and pull the trigger on these 3 PRs if everyone is ready. Then we need to fix our Travis setup. |
Tested all 3 pull requests. Everything works as expected, except when I test devel generate content it generates txt files as the OBJ and JP2 for Islandora Images. Is there a way to get it to generate images like it does for MEDIUM_SIZE and TN? Thanks for the clear instructions @dannylamb |
Hey @kimpham54, that is because @dannylamb had to use generic "file" media
entities instead of "image" media entities. The "image" media entities
don't seem to work very well with JP2 or TIFF images.
…On 1 Jun 2017 1:59 am, "kim pham" ***@***.***> wrote:
Tested all 3 pull requests. Everything works as expected, except when I
test devel generate content it generates txt files as the OBJ and JP2 for
Islandora Images. Is there a way to get it to generate images like it does
for MEDIUM_SIZE and TN?
Thanks for the clear instructions @dannylamb
<https://github.com/dannylamb>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#643 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACua4edvo-kNi6juc483ZqfyQNe_RobYks5r_mFIgaJpZM4NlEu5>
.
|
Thanks for testing y'all. I'm going to merge these. |
@kimpham54 Ha! That's awesome you actually checked out those files. I guess it does text as a sensible default. |
Finally closed with #65 |
…52)" (#653) This reverts commit 31d465fff07d06a35c3703168c9e2298fb72c672.
This is a long-term strategic move to more closely align islandora with the Drupal community. Drupal expects/wants you to use nodes and media to model your content (Media is becoming core in 8.4), so by falling in line we will open up access to a larger swathe of contributed modules and open up islandora to a much larger user community.
This is a large shift that will require PRs against all of our Drupal modules.
islandora
module. Any special actions done in response to entity CRUD events will need to get shuffled into node hooks. Remove any custom UI work for theadmin/content
menu.islandora_collection
and re-exportislandora_image
and re-exportWe can possibly use the
config:export:content:type (cect)
command with the Drupal console to do those re-exports.The text was updated successfully, but these errors were encountered: