authors | nicely formatted summary of authors

I have added two new sheets: "Erik Help" and "Authors".

The "Authors" sheet contains a single IMPORTRANGE formula in A1, which brings in all the data from your source spreadsheet. Then, formulas within the current spreadsheet can simply refer to the data in the "Author" page, instead of using more IMPORTRANGE references.

From there, I reference the "Author" sheet within one formula in C1 of "Erik Help" (i.e., the "ID" column):

=ArrayFormula({"ID";IF(A2:A="";;SUBSTITUTE(TRIM(TRANSPOSE(QUERY(TRANSPOSE(ARRAY_CONSTRAIN(IFERROR(VLOOKUP(TRIM(SPLIT(B2:B&REPT(",X";10);","));{Authors!B:B\Authors!A:A};2;FALSE));ROWS(A2:A);10));" ";10)));" ";", "))})

This one formula creates the header and all results for the column.

The formula itself is difficult to explain. But below are some of the key concepts.

REPT adds 10 repetitions of ",X" to the end of every string in B2:B. This assures that, when SPLIT we will have at least 10 items for each row. I chose the number 10, because it seems likely that no book will have more than 10 authors; and we will need uniformity for the rest of the formula.

SPLIT splits the string of author names and X'es into separate columns at the commas.

TRIM will remove extra spaces.

VLOOKUP will attempt to find every separate author name or X in a reversed array from the "Author" sheet, returning the ID number if found.

IFERROR will return null if nothing is found (which of course will happen for each X).

ARRAY_CONSTRAIN will limit the returned results to 10 virtual columns.

TRANSPOSE(QUERY(TRANSPOSE(... will create QUERY headers from all 10 results per row and then flip them to match the row-by-row data.

TRIM again makes sure there are no stray spaces.

SUBSTITUTE will exchange remaining spaces for ", ".

I think you want row_number():

I think the Lombok generated hashCode method is causing an infinite loop as Movie references Authors, each of which references the same instance of Movie.

You can probably confirm this by checking bytecode, or just ditch the @Data annotation and manually code equals and hashCode on Entities.

Alternatively you should be able to break the cycle with an @EqualsAndHashCode.Exclude annotation on the movies property of Author - https://projectlombok.org/features/EqualsAndHashCode

After all, the answer was quite easy as it has been part of the "product.component.html" page before the table view has been replaced by a list view.

The HTML tr tag featured the following jhiSort directive

Based on the provided target data structure above, you appear to be using a dictionary. It isn't clear what you would like your keys to be so I would probably suggest using a list/array.

I would suggest a slightly different way to dissect the problem.One potential implementation would be to iterate over each row (paragraph

of the table (div

From here, if the link(s) are present you could then query the external data source (or read from a different location on the page) to collect the respective data. In the example below, I choose to do this in a different iteration of data to help make the code a bit more readable.

I have not used the BeautifulSoap4 library before. I apologise if my solution isn't the most elegant regarding the libraries usage.

Note that the compile definitions basically work like preprocessor #defines; you need to make sure the compiler will be able to use the valus in a menaningful way. Note using a list variable like

This is how I've been using Dapper. Works great:

1. Make your Dapper method async.
2. Make the method or event that CALLS your method an async Task as well, so you can await the Task.
3. To return a list, do return (await blah blah blah).ToList();
4. Use the Async versions of all SQL calls.

Something seems a little off with your foreach loop. Would you mind explaining what you're trying to achieve with it? It seems like your first query should return all the models you need.

Example:

From your question it was not immediately obvious what the problem is (hence the lack of engagement). After playing around with the code and the API for a bit, I now have a much better understanding of the issue.

The issue is that the Google books API does not always include an image thumbnail for each of the items.

Your current solution for this issue is to retry the entire search until all the fields have an image thumbnail. But think if this is really needed. Maybe you can split it up. In my testing I've seen that the books without image thumbnails often switch. Meaning that if you just keep retrying until all the results from the query have a thumbnail, it will take a long time.

The solution should attempt to query each book individually for the thumbnail. After X number of tries it should default to a 'image available', to avoid spamming the API.

As you already figured out in your post, you can get the volume ID of each book from the original search query. You can then use this API call to query each of those volumes individually.

I've created some code to validate that this works. And only one book does not have an image thumbnail at the end. This code still has a lot of room for improvement, but I'll leave that as an exercise for you.

There is no "universal" meaning behind this. It could be a number of things:

• Data not present
• Not applicable
• Use case specific information
• Error in the dataset itself
• ...

If you want to create value out of this data, don't make assumptions, look for documentation or description of dataset, which describes its columns, types and expected content. The owner or creator of this dataset should of course also be able to inform you of what it represents.