-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add OriginalFile display to IIF Manifest view #66
Conversation
@alxp today I am starting the testing of this PR, and I have my first question. I will be using ISLE2 to test PR, and I am not 100% sure which ISLE2 "Make target" I should use to make sure I have met your testing requirement of importing islandora_defaults feature. In case you don't know I can ask in the "tech call" or Slack. Thanks. |
Hi @ysuarez, thanks for taking a look at this. You just need to be able to run a Drush command, so make demo may not be a good choice if I recall correctly. Make local or any other should b fine. Let me know how you get on. |
@alxp I just made my first attempt to test this, but I suspect I am doing something wrong or I am being tripped up by the isle-dc main branch still having some issues. Here is what I tried so far....
Then I got this error...
Let me know what I need to do different or if you have any other suggestions. BTW, the only "content creation" options Drupal gave me were "Article" and "Basic Page," but I expected to have an option for "Resource Node" when using |
Hi Yamil, I don’t have Isle active right now, but it sounds like Islandora Defaults might not be installed in your current environment. Can you check to see if it is enabled? If not you can enable it and that should also work
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Yamil ***@***.***>
Sent: Wednesday, May 11, 2022 11:14:38 PM
To: Islandora/islandora_defaults ***@***.***>
Cc: alxp ***@***.***>; Mention ***@***.***>
Subject: Re: [Islandora/islandora_defaults] Add OriginalFile display to IIF Manifest view (PR #66)
@alxp<https://github.com/alxp> I just made my first attempt to test this, but I suspect I am doing something wrong or I am being tripped up by the isle-dc main branch still having some issues.
Here is what I tried so far....
* make local
* docker-compose exec drupal with-contenv bash
* drush fim -y islandora_defaults
Then I got this error...
In FeaturesCommands.php line 758:
No such feature is available: islandora_defaults
Let me know what I need to do different or if you have any other suggestions. BTW, the only "content creation" options Drupal gave me were "Article" and "Basic Page," but I expected to have an option for "Resource Node" when using make local off of the development branch. Though I could be wrong.
—
Reply to this email directly, view it on GitHub<#66 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAAUD3DODEQMJXSZ4QHUUITVJRSQ5ANCNFSM5U4CUBAA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@alxp I just spent some time trying to check if islandora_defaults is enabled (after running Since I am still learning about using and managing Drupal Features (with a capital "F"), I am not sure if isladnora_defaults can be installed the same way as a regular Drupal module. I did run BTW, my apologies for not knowing how to proceed. At this point I think I may need to run something like Let me know what you suggest. @seth-shaw-unlv do you have any suggestions for me? |
Copying from Slack:
That is the same as non-ISLE. If you're still stuck let me know.
|
So, @ysuarez, testing stuff in ISLE has been a bit of a pain. Most recently I've used Islandora-Devops/isle-dc#248 and then done I haven't gotten If you want to use |
Quick update, today I ran
but I guess I am putting in the wrong branch value, since I got this error...
|
Looks like you are missing an "i", and normally you would add "dev" to get a branch: |
Hi @ysuarez There's a slightly confusing thing with composer that you've run into: The default place that composer looks for packages is on packages.org . There is an islandora registered namespace there, but it is not always up to date with non-head branches since it isn't directly part of GitHub. The easiest way to get the branch you want is when you're logged in to the server, remove the existing islandora_defaults module and clone it from Github. Then you can check out the branch directly on the command line with Git. The other option that plays more nicely with composer is to add a repositories: {} entry in composer but for short term testing it's not as necessary. Best,
|
@alxp thanks for the explanation, it all makes sense. I can try the approach of removing existing then cloning islandora_defaults then switching to your PR's branch. I am also curious about how to set up composer.json to pull the PR's branch, I will do some googling. |
After running I erased the cloned repo and went back to running...
This time making sure I had three the letter "i" in IIIF, since I know I originally caught that that I was missing an "i," but noticed that Seth mentioned it too. Looks like I did not properly combine the 3 "i" and "dev-" on Wednesday tests. I still got an error, but maybe this one is an easier one to work around compared to manual repo cloning...
The current contents of the root composer.json's "require section for
Thoughts? |
I went back to running 'make local' and cloned the islandora_defaults repo in I was able to use composer to install the islandora_default dependencies
I also tried running I will now attempt to finally test this PR, though let me know if anyone thinks I have done something wrong so far. |
Here are the results of my testing tonight...
At this URL.... The output is empty straight brackets... I may have done something wrong, so let me know what folks suggest. BTW, one thing that I thought worked well in my "cloned repo" approach was that by using the current |
Hi @ysuarez ,
Thanks,
|
No, also empty brackets for output.
I see some errors during the time I created the nodes and added the media files, but not sure if there is a smoking gun here or run-of-the-mill errors. I am attaching a zipped copy of the HTML table that has the recent Drupal error messages, in case it is helpful. (Note: I needed to zip it to attach it to comment.) PR 66 Drupal error log.html.zip I am also adding a screenshot of what the recent Drupal errors look like. @alxp or @seth-shaw-unlv, let me know if you want me to post the details of any of these log entries.
No, I am getting a status of 200 for both manifest URLs... https://islandora.traefik.me/node/1/book-manifest-original For the record, @alxp feel free to have someone more knowledgeable than me try to test this PR so it will take less time. Though I am happy 100% to keep trying new ways to test this PR properly, and have been learning a lot in the process. |
HI @ysuarez , I've updated the testing instructions at the top of this ticket. A couple of things to note that may have caused it to not work for you:
If you try again and have any trouble you can reach me on Slack and we can go through it together. Thanks for your efforts on this.
|
@alxp quick update. I tried again using my previous ISLE2 instance from a couple of weeks ago. I just ran I then updated the model to "Page" for my existing child nodes and the two manifest URLs were still blank. Then I created a new parent node and two new child nodes (using memberOf) with the updated model instructions and still got empty manifests. I can now try to build the instance again from scratch using Maybe it may be time to work together on Slack when I do this to see if you catch any issues I am creating or missing. |
I just checked to see if one of the related Drupal views for this PR was installed/enabled, and it seems it has. I visited... |
@ysuarez - in your error log above it says it can't find book-manifesty - note the extra y |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I built a shiny new box with local-install-profile
, the only branch which has been reliably building for me lately.
I manually updated both Islandora and Islandora defaults, then switched to the iiif_original
branch
The Mirador display context has to be set manually paged content
nodes.
https://islandora.traefik.me/node/3/book-manifest-original shows the original file
https://islandora.traefik.me/node/3/book-manifest shows service files
What does this Pull Request do?
Add a display to the IIIF Manifest view that contains media tagged as OriginalFIle.
What's new?
Just a new display mode for IIF manifest.
How should this be tested?
If islandora_defaults does not have a .git subfolder, do the following:
Repository item with model "Paged Content
1 or more Repository items with model Page, and MemberOf relationship to the Paged Content item
Media of type "File" for each of the Page items, containing a TIFF file.
Additional Notes:
Some types of files such as maps aren't served well by the JPG ServiceFile which is of limited resolution.
Interested parties
Tag (@ mention) interested parties or, if unsure, @Islandora/8-x-committers