go to post Scott Beeson · Mar 15, 2017 > When the instance is Locked or AdminLocked, no changes can be made via Studio. What about via ensemble namespaces? I'm trying to use the "Deploy Production Changes" utility and it says it is locked. Bill from Managed Services says he unlocked it, but it still says it is locked for me.edit: This should have been a comment...
go to post Scott Beeson · Mar 13, 2017 Personally I think I would prefer the output to be streamed as it is received. Perhaps this could be an option? Live output vs "Output in progress" as you suggest?
go to post Scott Beeson · Mar 13, 2017 I got this while importing the classes... any ideas? edit: Nevermind, I just hit back then import again. It worked. /shrug HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Set-Cookie: CSPSESSIONID-SP-57772-UP-csp-sys-=008000010000rGtpFVtkj20000ApozxNVGmmNXNIMCWko6aQ--; path=/csp/sys/; httpOnly; CACHE-CONTROL: no-cache DATE: Mon, 13 Mar 2017 15:10:15 GMT EXPIRES: Thu, 29 Oct 1998 17:04:19 GMT PRAGMA: no-cache Transfer-Encoding: chunked Set-Cookie: CSPWSERVERID=fcc28c73d69ac223d5063debc53f259f1ee904fe; path=/; httpOnly; 91 <P><P><B><FONT COLOR="RED">CSP application did not respond within the timeout period</FONT></B><P> The processing of the request was interrupted 0
go to post Scott Beeson · Mar 13, 2017 Yes, please, for the love all things holy!Evgeny, can't you just edit it to include a snippet?
go to post Scott Beeson · Mar 13, 2017 You're really trying to get those Global Masters points, aren't you?
go to post Scott Beeson · Feb 24, 2017 Based on the docs you linked, I found /csp/healthshare/<namespace>/EnsPortal.Deployment.DeployProductionChanges.zenThis allowed me to select a "Deployment" and successfully accomplish my goal. This is terribly unintuitive. Not only is the context completely different, but there is no parity among terminology. To improve this, there are two options:1. Change the "Export" process. First, it should not be called "Export", it should be called "Create a Deployment" or "Create Deployment Package". Second, it should not be in the actions for the adapter/operation, it should be in the main Ensemble menu.2. Change the "Import" process. First, it should be called "Import" and not "Deployment". Second, it should be in the context of the production, located in a similar place to the Export button. Ideally, you would click "Production Settings" and there would be an "Import" button there.
go to post Scott Beeson · Feb 24, 2017 I could probably be convinced either way, however at some point you have to wonder, if a post has so many disparate threads/conversations, is the topic too vague? Perhaps a new post is warranted.I think of both extremes. Reddit is 100% threaded and gets very out of hand, but StackOverflow is only minimally threaded (each answer has comments). I think it works well there, but I suppose these forums fall somewhere in between. It's not a simple question/answer site, but a place for discussions as well. I grew up on dial up BBSs and later phpBB though, and non-threaded conversations were just a way of life that I never noticed a problem with.As Evgeny said, perhaps we just wait for it to be a problem, then try to come up with a creative solution. edit: for what it's worth, many modern forums have the option of "Flat, Threaded or Hybrid" views. Also, here's an interesting take on the subject.
go to post Scott Beeson · Feb 24, 2017 Maybe he's realizing that fragmentation is bad. Fingers crossed.
go to post Scott Beeson · Feb 24, 2017 These namespaces span multiple servers, so I think that rules this out? Also, each of the copies will have minor changes (each FTP out adapter will have a different filename prefix, etc). Plus, it sounds super complex for this simple use-case. edit: But I appreciate the quick response, and mapping sounds really cool otherwise!
go to post Scott Beeson · Feb 16, 2017 I may have realized what I was missing. These "documents" are generated on the fly so I guess you wouldn't be able to reference a static table of document contents. I was led to this by running the following query on the first 15k rows or so.SELECT DocumentId, HomeCommunityId, RepositoryId, count(AggregationId)FROM HS_IHE_ATNA_Repository.DocumentGROUP BY DocumentId, HomeCommunityId, RepositoryIdThese are the numbers of duplicates198042174634754163526247082 ie, only 2 documents were duplicated 8 times. The vast majority only had a single entry. Still, if we extrapolate this out, that's a lot of duplicated data in my opinion. If my math is correct, in this sample, 21% of the documents records are exact duplicates.
go to post Scott Beeson · Feb 16, 2017 I'm not really talking about speed or performance. It just seems strange to me to have a table that stores "document base data" in an event based format. I'm not sure if I'm being clear, so let me see if I can provide a visualHere is a representation of the way I understand it to work: And here is what I would expect to see: Am I missing something?
go to post Scott Beeson · Feb 16, 2017 We can add HIE tag, would you please point the related articles and questions?This would be great, thanks. I can start a topic eventually with links to posts that should be tagged, but probably not today. Although, it would be really nice if community members could tag posts freely.
go to post Scott Beeson · Feb 16, 2017 I'm actually a spambot designed to get responses. Someone just pointed me at the wrong domain.
go to post Scott Beeson · Feb 14, 2017 So can you answer the question: Does this mean that if the same document was requested 1,000 times that there will be 1,000 entries for it in the .Document table?
go to post Scott Beeson · Feb 14, 2017 I use this a lot as well, but I really wish it could magically search across our kajillion different HealthShare servers/namespaces. :(
go to post Scott Beeson · Feb 7, 2017 Looks like it's the .indented class. It adds a left margin of 44px to each child comment. If it could somehow only be applied to the first level comment I think that would be ideal. The compromise is that we lose multi-threaded conversations, but yet again, I have to point to Stack Overflow. I think we would adapt pretty well.