-
Notifications
You must be signed in to change notification settings - Fork 15
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
How to identify error source? #113
Comments
Nothing useful in the Apache log either:
|
@bondjimbond let's do a walk through together. IMI produces an entry inside your Drupal Log (see your admin/reports) that has all the settings you passed during an IMI ingest setup (its like a full ARRAY dump). Can you share that with me? That will allow me to retrace your steps one by one There are two types of errors: PREPROCESS: (the ones you are seeing)Most of the time those errors are either:
Actual ingest
All these try to generate verbose messages that go into your Drupal Log. All of that, is generated in this file (e.g a line there)
Will wait for that Drupal Log output and test your data, i don't see anything obvious wrong on your CSV so better that way. |
Absolutely, thanks for helping. I'm using the same sample.mp4.zip that I had used successfully with the stock CSV and Twig templates, so I don't think there's a problem with the object/zip file itself. I had initially set the incorrect parent collection, but fixed that, and am still having these problems.
|
@bondjimbond hi,np, ok, first thing (not related to your error), but i don't see your Twig Template being used as source for the MODS datastream, its not mapped in those settings. OK, i used your CSV, added your template to the IMI template list Which means your settings are off. Other than the missing Template mapping for MODS i see this one [parentmap_row] => Array
(
[parentmap] => 0
[parenttype] => 1
) Which for your CSV should be [parentmap_row] => Array
(
[parentmap] => 4
[parenttype] => 1
)
Give it a shot again. I feel a short tutorial (Zoom or so) next week could help you. You are pretty much there, just probably just moving too fast between settings, and i know, there are a lot of them |
@McFateM is a pretty veteran (in terms of knowledge, he is pretty young!) user, maybe he can give you a hand and i also know ISLE has done some work around documenting and hacking IMI. Maybe he can help here too? |
Ah, right, I think it was the And good to know that I have to select the Twig template again -- I had thought that by selecting it on the Templating section, that would be how it's selected for the whole thing. What are the odds of some of these configurations being preselected, or at least prepopulating the selections based on input from earlier on in the process? |
Sorry I'm so late to this conversation... I'm not as young as Diego suggests. 8^) And very busy. I have a hook and some IMI customization that pre-populates EVERYTHING. It's something I wrote just before IslandoraCon last Fall. I think there's some mention, maybe even some "documentation" in my blog from back then. If you're interested I can take a look back sometime this afternoon and post links here to anything I find? |
@SummittDweller Thanks, that would be helpful. It'd be nice to have some prepopulating done, as it's easy to skip over small but important settings by accident. |
@bondjimbond the first twig template selection is more like a playground/testing, not really needed, specially given the fact, that you could eventually want to have different twig templates for different CMODELS or even force your own DC template overriding what Islandora does. Means you can end with many twig templates in use at the same time. That preset thing has been in the wish list for quite some time but i always stumble in the same issue, what happens if the CSV changes? Probable @SummittDweller solved that one! (cool new handle by the way!) |
@DiegoPino Err, no I didn't solve that problem. However, in my case, the CSV layout is ALWAYS the SAME, no matter what CModel. I did remember correctly, there is some "documentation", but it's paper thin. @bondjimbond You can find it at https://dlad.summittdweller.com/en/posts/049-granular-isle-customization-implementing-imi-hooks/, and specifically in the last link (a gist) in that post. Have a look if you like, and let me know if you're interested in the same, I might be able to make a little time to assist with implementation. |
Thanks, I'll look at that when I have the time! I recorded a brief screencast on using IMI for my members; might be useful to others if they ask for help figuring this out (they can learn from my stumbling): https://www.youtube.com/watch?v=LhgK5-doWJE |
I've been working on my Twig template and CSV template. Metadata templating is coming out just fine, but when I reach the Ingest step, I get the following error:
messageRows with issue(s) that could not be translated to Objects: 1,2
I've only got the one row, so I know which row the error is in... but how can I identify what the actual problem is? I'm not doing that much different from when I was testing using the example files, just adding more metadata fields.
OBJ maps to the "filename" column.
I would of course like help identifying the source of the error in my CSV, but I would like to see IMI provide a bit more detail. I see that it prints an array to the Drupal log; perhaps the error could refer more precisely to the exact position in the array where it's hitting an error and log it?
arca_imi.zip
sample.mp4.zip
The text was updated successfully, but these errors were encountered: