You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered an issue with the metadata in spreadsheet load for the 300+ RISE posters. For each load I've submitted the first creator role is skipped and the second role is applied to the first creator name, the third creator role is applied to the second creator name, and the third creator name doesn't get a role at all.
It's possible there's an issue with how I've constructed the spreadsheet, but I've tried a dozen or so edits without any luck (hence the dummy values in the table above). The spreadsheet validates, so there aren't any obvious issues with the spreadsheet itself, and the loader is reading the role values since they're being added to the XML for second and third creator names. I'm just not sure why the first creator role isn't being read or accepted or why the roles are being shifted to other creator names.
The text was updated successfully, but these errors were encountered:
I've encountered an issue with the metadata in spreadsheet load for the 300+ RISE posters. For each load I've submitted the first creator role is skipped and the second role is applied to the first creator name, the third creator role is applied to the second creator name, and the third creator name doesn't get a role at all.
So submitting:
Generates this:
It's possible there's an issue with how I've constructed the spreadsheet, but I've tried a dozen or so edits without any luck (hence the dummy values in the table above). The spreadsheet validates, so there aren't any obvious issues with the spreadsheet itself, and the loader is reading the role values since they're being added to the XML for second and third creator names. I'm just not sure why the first creator role isn't being read or accepted or why the roles are being shifted to other creator names.
The text was updated successfully, but these errors were encountered: