Alex did it automatically for AC with a script for all the WeBWorK problems that had a source address, which was almost all of them. He did it so that the label is more or less the same as the address, except replacing problematic characters with non-problematic characters.
I thought the idea was to have the label be more about the problem content and that this was a stopgap measure, but having the label be the source was actually really helpful to me as an instructor because when a student reported a problem or issue with a problem in Runestone, I can see the label on the Runestone Instructor assignment tab and know what the source is. Then I can open it up on my WeBWorK server to take a peek, or report an issue here (like with the weird randomization effect in a few problems) or to WeBWorK if there's actually a bug.
But I was also in the perhaps unusual situation that I knew ahead of time that I wanted to assign all the WeBWorK problems that existed in the sections, so I didn't care about the label telling me about the content.
Although, when I was creating Runestone assignments I had to click on and preview each and every problem anyway, in order to confirm how many answer blanks there were to make the problems worth that many points, because Runestone didn't handle fractional points in the way I expected it to (it would round to the nearest whole number, so that a student who got 1 out of 2 answer blanks correct would get full credit for the problem if the problem was worth 1 point). I didn't experiment to see if that changed when the grading table changed to better handle WeBWorK problems, or if that's still the case.
Matt created the labels non-automatically for the few problems that were written into the PreTeXt source. So if APEX's problems are more of that kind, I have no ideas for you.
Chrissy