Project Coordinator tasks
1. Logging in
You need to log in to MISO LIMS in order to make changes to any LIMS entities. Logging in lets MISO record any changes you make on entities you have access to. If you are a new user and have not been given a username and password, you will first need to get a username and password by following the steps in the Adding Users section.
Try to log in now:
- Click on http://miso.gsi.oicr.on.ca.
- Enter your username (e.g. jdoe) and password and click the Login button.
If all goes well, you should see the MISO Dashboard and see a message at the top right: "Logged in as: jdoe".
1. Logging in
You need to log in to MISO LIMS in order to make changes to any LIMS entities. Logging in lets MISO record any changes you make on entities you have access to. If you are a new user and have not been given a username and password, you will first need to get a username and password by following the steps in the Adding Users section.
Try to log in now:
- Click on http://miso.gsi.oicr.on.ca.
- Enter your username (e.g. jdoe) and password and click the Login button.
If all goes well, you should see the MISO Dashboard and see a message at the top right: "Logged in as: jdoe".
2. Creating projects
A Project contains information about a set of Studies that may comprise many different Samples, Experiments and Runs. Samples are attached to Projects and they are often processed into Libraries and then Dilutions, which are then Pooled and sequenced. Projects also have Overviews, which hold information about a Project proposal. In this part of this workshop, we will create projects, set permissions, and familiarize ourselves with the project overview page.
Projects represent a sequencing effort toward a particular goal, usually led by a particular group or principal investigator.
In this workshop, you will make your own project where you will create samples, libraries and other entities.
Most pages have a "Quick Help" tab at the top right under the Save button where you can find basic information about the current page.
2.1 Create a new project
To create a new project:
- After logging in, click the My Projects tab at the top of the MISO dashboard.
- Select the Add button at the top right corner.
The Create Project page will display with a number of fields that you can fill in.
- Ignore Project ID and Name, since they are set by MISO once the Project is saved.
-
Enter a unique Alias. The alias is a name, chosen by us, that is associated with a project. The aliases must be a unique and contain only letters or numbers. It cannot contain spaces or punctuation. e.g.
DoIt4Science
(be creative!). Record this alias in your worksheet. -
Leave the Short Name field blank.
- In the Description field, enter
MISO training workshop [Date]
- Choose the amount of Progress that your project has accomplished:
- Unknown : I was told to enter this data and I does what they tells me.
- Active : We are receiving/have received samples and are actively working on this project.
- Inactive : Project is not yet done, but waiting for external collaborators, REB approval, papers to be published, etc.
- Cancelled : Project was scrapped because we did not get funding/samples/REB approval.
- Proposed : Project Initiation form has been received and is awaiting go-ahead by Genomics leadership.
- Pending : We are waiting for the project to start.
- Approved : Project has been approved by Genomics leadership.
-
Leave the Reference Genome as
Unknown
. - In the Permissions section, select
your name
from the Owner drop-down. -
Make sure that Allow all internal users access? is selected.
- Click the Save button at the upper right.
Upon save, you will be taken to the Edit Project page, where you can see the project you just created. Notice that the Project ID and Name now have values. The Project ID will be an integer, and the Name will begin with PRO. These are specific to this project and used by MISO to track the project internally.
2.1.1 Add a Study
In order to make sure MISO is SRA-compliant, you must add a Study to your Project. Studies are legacy objects that are not really used in the current system, but need to be added anyway.
- Click on the Studies section to expand the section.
- Click Add at the top left of the table.
- Much like creating a Project, enter:
- Alias (letters and numbers only): this can have any name, but make sure it is recognizable as belonging to your Project.
- Description: any free-text description
- Select a Study Type from the drop-down menu : Unless you are certain of the
sequencing type, select
Other
. - Click the Save button at the upper right.
2.2 My Projects tab
- Click again on the My Projects tab.
You will see a list of all of the projects you have access to in MISO.
- Find the project you just created in the list. You can sort any column in the table by clicking the column header. You can also search for your project by any of the displayed columns and the table will filter as you type.
- Click on the link in the Project Name, Short Name or Alias (they all go to the same page).
2.3 Edit Project page
The Edit Project page is used for viewing basic information about a project as well as all of the entities associated with that project, such as the samples, libraries, pools, and runs.
Once you create different entities for your project like Samples, Libraries, Library Dilutions, Pools and Runs, you can view and search them on this page. Each section can be expanded by clicking on its name or the arrow next to it. The tables under each section can be sorted by the column header or searched using the field in the upper right. The Options menu above the search bar contains actions you can perform on the entities in the project.
2.3.1 Add a project overview
Project Overviews specify the origin of a specific set of samples that are part of the project. For example, if you are receiving some samples from a clinician and other samples from a hospital, you can enter the expected numbers of samples from each and indicate how many of them passed quality control and what stage of preparation has been completed. Project overviews are optional and only used to indicate overall progress on the My Projects page.
- Click Add Overview at the right side under the Project Information.
- In the pop-up, enter a principal investigator (
You Yourname
!) - In No. proposed samples, enter
5
. - Click the Add Overview button.
The Edit Project page will reload and now there will be a table with your name under the Project Information section. You can fill in other values if you wish, or leave them blank for now. You can also select the checkboxes below the table to show that certain stages have been completed. Remember to press the Save button after you are finished editing.
2.3.2 Add Project Files
In the Project Files section, you can add attach any necessary documents to the project (e.g. Project Information form, REB).
- Click the Project Files section on the Edit Project page.
- Find a document or image that is appropriate for your study
Now that your project has been created, continue to make your first samples.
| < Admin tasks tutorial | Home | Samples tutorial > |


{{Statename}}
Persons Arrested - Male
{{peoplearrestedmale}}
Persons Arrested - Female
{{peoplearrestedfemale}}
Persons Arrested - Total
{{peoplearrestedtotal}}
Persons Chargesheeted - Male
{{peoplechargedmale}}
Persons Chargesheeted - Female
{{peoplechargedfemale}}
Persons Chargesheeted - Total
{{peoplechargedtotal}}
Persons Discharged - Male
{{peopledischargedmale}}
Persons Discharged - Female
{{peopledischargedfemale}}
Persons Discharged - Total
{{peopledischargedtotal}}


And lo! there came unto Gath an man whose head was as the head of the otter.
And his body also was as the form of the otter and likewise his dimension.
And when the man spoke his voice was as the cry of the otter.
Now the people of Gath, seeing this, were much afraid.
They gathered about the man with their pointy sticks and led him unto their Hierophant.
Now the Hierophant of Gath dwelt in a place of much mist and vapourousness unyielding.
And the people said “O Hierophant of Gath, we bring you this man in form like unto the otter, what shall we do with him?”
And with his mouth the Hierophant of Gath spoke mumbo-jumbo unto them and they laid down their pointy sticks and returned to their fathers' fields where many tares were sown.
And he took the man like unto the otter into his house in the mists.
And the next day there came tidings of the Hindenburg disaster.


FACULTY EXPERTISE SYSTEM
HOME
FACULTY
ADMIN
NEW USER
FACULTY LOGIN
ADMIN LOGIN
LOGIN.
NEW USER LOGIN


Runtime Modulus Tests
These tests test the non-built modulus functionality. (runtime only, no node.js build process)


Preparation time
30 mins to 1 hour
Cooking time
1 to 2 hours
Serves
Serves 6-8
Dietary
Preheat oven 160C/320F/Gas 3.
Grease and line the base and sides of an 20cm/8in deep, round cake tin with baking parchment.
Measure all the cake ingredients into a large mixing bowl and beat well until thoroughly blended. Place half the mixture into the prepared tin and level the surface.
Take one third of the marzipan and roll into a circle the same size as the cake tin, place the circle on top of the cake mixture. Spoon the remaining mixture on top of the marzipan and level the surface.
Bake for about one and three-quarter to two hours or until golden brown and firm in the middle. If toward the end of the cooking time the cake is getting too brown, loosely cover with a piece of foil. Allow the cake to cool in the tin before turning onto a cooling rack.
When the cake is cool. Brush the top with a little warmed apricot jam. Roll out half the remaining marzipan to the size of the cake and sit it on the top. Crimp the edges of the marzipan and make a lattice pattern in the centre of the marzipan using a sharp knife. Make 11 even sized balls from the remaining marzipan and arrange around the edge.
Brush with beaten egg and glaze under a hot grill for about five minutes, turning the cake round so it browns evenly, so the marzipan is tinged brown all over. (You can also do this with a blow torch if preferred)
To crystallise the flowers, lightly whisk the egg white in a bowl then carefully brush over the flower petals.
Sprinkle over caster sugar so the sugar sticks to the egg white. Leave to harden in a warm place, such as a shelf above a radiator or in an airing cupboard, until dry and firm.
Carefully remove from the rack and arrange in the centre of the cake.


Mesoscale Activity Viewer¶
This is the new and improved unit viewer for the Mesoscale Activity Project.
Installing¶
For Windows users, head over to Releases and select the latest version for an installer. Simply extract the zip file and double click “Activity_Viewer_0.1.0.exe”.
N.B.: This release has not been signed. If this concerns you, you can use the installation method in the Development section below.
Mac and Linux users, until we can build and distribute binaries, you should also use the Development instructions below.
Development¶
Prerequisites¶
We’ve tested this software on Python 3.7. It’s conceivable it could work on an earlier version of Python 3, but we won’t support it. I strongly recommend using Anaconda. Windows users will want to use the Anaconda Prompt. Linux and Mac users should be able to get by with your favorite terminal emulator.
We use virtualenv to create a local
Python environment. If you’re using Anaconda, conda install virtualenv
should get it for you. If you don’t like Anaconda, you can do
python3 -m pip install --user virtualenv
instead.
You’ll also need to have Node.js 12 or later with
Yarn installed. After installing Node,
npm install -g yarn
will get Yarn for you.
Setting up¶
Make sure your Python interpreter is the one you’re expecting:
> $ which python3 # where.exe python3 on Windows
/home/alan/anaconda3/bin/python3
Once you’ve satisfied yourself that this is the correct Python, create and activate a new virtual environment, then install dependencies:
> $ python3 -m pip install --user virtualenv
> $ python3 -m virtualenv venv
> $ . venv/bin/activate # on Windows: .\venv\Scripts\activate
(venv) > $ python3 -m pip install -U -r requirements.txt -r requirements-dev.txt
(venv) > $ python3 -m pip install -e .
(venv) > $ cd app && yarn install && cd .. # on Windows: cd app; yarn install; cd ..
After all the dependencies are installed, do a quick sanity check:
(venv) > $ pytest # or tox (slower, but sets up a self-contained environment) if you prefer
Now you can start hacking.
Running the viewer¶
If you installed the binary on Windows, you should see an Activity Viewer entry in your Start menu. Simply double-click that and the viewer will start up.
Otherwise, you’ll need two terminals.
In the first terminal, activate your virtualenv and run viewerd start-daemon
.
In the second terminal, cd
into the app/ directory and run yarn start
.
After a few moments, the frontend process will fully load.
On startup, the viewer prompts you to load a settings file or some data files, which you can do by selecting the appropriate option from the File menu. Selecting only data files will use the default settings, or you can specify data files within your settings file.
For a description of the formats of the settings and data files, please read this section of the docs.
Current limitations and known issues¶
Choppy camera motion when dev tools are engaged¶
Moving the brain about in the viewer window may lag a bit when the dev tools are being displayed. If you don’t care about console output, simply close the dev tools.
Python 3.8¶
On Windows (we haven’t tried on Linux or macOS), trying to install dependencies
via pip
will throw something like the following error with Python 3.8 on
building the statsmodels wheel:
ModuleNotFoundError: No module named 'numpy'
As a workaround, if you do
(venv) > $ python3 -m pip install numpy==1.8.5
(venv) > $ python3 -m pip install -U -r requirements.txt -r requirements-dev.txt
the dependencies should install correctly. You may also need to install the latest C++ Build Tools.
Acknowledgments¶
This work was supported by the Mesoscale Activity Project. Parts of the UI code, especially the WebGL shaders, are based off of or otherwise inspired by work done previously by Patrick Edson for the Mouselight Neuron Browser.
Quickstart¶
After you’ve installed the Activity Viewer, head over to the Usage section to learn more about how to work with your data.


--- title: UX Discovery permalink: "/recipe" layout: page table_labels: column_1: Task column_2: Time (Days) column_3: Rate column_4: Total print_tooltip: Print reset_tooltip: Reset calculate_tooltip: Calculate --- {% include navbar.html %} {% include pageHeader.html %} {% include ingredients.html %} {% include summary.html %}


Netwulf was made by Ulf Aslak and Benjamin F. Maier. If you use this software please cite our paper. The code for this project is available on Github. The Python package netwulf is an API to this web app. Documentation is available here.


Languages & tools come and go, but listing them helps form a mental picture of a candidate.
I've also picked up and done some work in C, Java, Python and Ruby, PostgreSQL and others.


{% extends "template.html" %} {% block main %}
It's often useful to be able to start a server with a self-signed cert. The following code starts a web-server on HTTPS port 9443 with a simple handler:
{{ source("HttpsSelfSignedCert.java") | raw }}To use a signed certificate, you need to create an {{ javadoc("io.muserver.HttpsConfigBuilder") | raw }}
and pass it to the withHttpsConfig
method on the {{ javadoc("io.muserver.MuServerBuilder") | raw }} class.
The {{ javadoc("io.muserver.HttpsConfigBuilder") | raw }} has a number of useful ways to create a context, for
example you can load a cert from the file system, classpath, or an InputStream
.
You can also specify which TLS protocols and ciphers you would like to use.
{{ source("HttpsWithCert.java") | raw }}To perform a hot change of an HTTPS certificate, construct a new HttpsConfigBuilder
and change it
using the MuServer server reference:
server.changeHttpsConfig(httpsConfig);
HTTP Strict-Transport-Security instructs browsers to only access your website via HTTPS. This is achieved
by setting the Strict-Transport-Security
response header.
For convenience, the {{ javadoc("io.muserver.handlers.HttpsRedirectorBuilder") | raw }} class can be used to generate a handler to do this for you. Just tell it the HTTPS port to redirect to, and the amount of time the directive is valid for.
{{ source("HSTSExample.java") | raw }}If you omit the HSTS config on this builder, it will redirect to HTTPS without setting HSTS headers.
Getting free, automatically renewed certificates with Let's Encrypt and other ACME-based Certificate Authorities is even simpler than providing your own SSL config.
See the Let's Encrypt integration documentation for details.
Mu Server is based on Netty, and Netty recommends that OpenSSL is used due to it being faster and having JDK-independent ciphers. In order to support OpenSSL, please follow the netty-tcnative wiki page.
If running on a modern Linux distribution, it may be enough to add the following dependency:
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-tcnative-boringssl-static</artifactId>
<version>{{ artifactVersion(groupId="io.netty", artifactId="netty-tcnative-boringssl-static") }}</version>
<classifier>linux-x86_64</classifier>
<scope>runtime</scope>
</dependency>
The sslInfo()
method on the {{ javadoc("io.muserver.MuServer") | raw }} class returns an
{{ javadoc("io.muserver.SSLInfo") | raw }} object that can be used to get the actual values your server supports. In a handler,
this can be accessed with request.server().sslInfo()
and the following
table shows the settings from this website:
| Property | Value |
|---|---|
sslInfo.providerName() |
{{ sslProvider }} |
sslInfo.protocols() |
{{ sslProtocols }} |
sslInfo.ciphers() |
{{ sslCiphers }} |
sslInfo.certificates() |
|
To see which TLS versions and ciphers your users are connecting with, you can refer to the connection info exposed by Mu Server.
To see an SSL report for Mu Server using OpenSSL, go to the SSL Labs SSL Report for muserver.io.
To allow authentication with client certificates, create a Trust Manager and pass it to
withClientCertificateTrustManager(TrustManager)
on the
{{ javadoc("io.muserver.HttpsConfigBuilder") | raw }}. You can then access the client cert (if sent and valid)
with the MuRequest.connnection().clientCertificate()
method from any handler.
See the Mutual TLS documentation for a full example.
{% endblock %}


new require("TickerView")(opts)
TickerView is a view of Streamhub data that is structured as a horizontal ticker, similar to television media's ticker, time based, LTR. When the feedCollection option is specified, the ticker view will use the content items in the feedCollection to populate the Y-axis of the ticker, stacking all feedCollection items above the appropriate Ticker items, based on the create date of the content.
Parameters:
| Name | Type | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
opts |
Object.<string, *> | A set of options to configure this instance. Properties
|
- Source:
- TickerView.js, line 23
- Source:
- TickerView.js, line 1
Members
-
<inner> className
-
- Default Value:
- hub-TickerView
- Source:
- TickerView.js, line 65
Properties:
Name Type Description className
string The css class name that this object will apply to it's holding element
Methods
-
<protected> _addFeedItem(item, col)
-
Adds feedCollection items to the appropriate collection for the child FeedTickerViews.
Parameters:
Name Type Description item
Object The new feed item that is to be inserted into the child.
col
Backbone.Collection A reference to the feedCollection that item came from.
- Source:
- TickerView.js, line 257
-
<protected> _animateAdd(itemEl, col, index)
-
Helper function to abstract the animation process on insertion. At this point in time, the item's main element has not been inserted into the DOM. It is the responsibility of this method to add the element to the DOM in any manner that it sees fit.
Parameters:
Name Type Description itemEl
Object The $html element for the item that is to be inserted.
col
Backbone.Collection A reference to the collection that this item was added to.
index
number The index in the collection to find the original item.
- Source:
- TickerView.js, line 159
-
<protected> _insertItem(item, col) → {Object}
-
Inserts a new piece of content into the dom. Used as a callback handler for collection.add events.
Parameters:
Name Type Description item
Object A piece of content that was streamed to this view from Streamhub.
col
Backbone.Collection A reference to the collection that this item was added to.
- Source:
- TickerView.js, line 92
Returns:
The $html element that was inserted.
- Type
- Object
-
<protected> _rebalanceFeedItems(item, col, index)
-
Helper function to rebalance feed items whenever we receive a main Ticker item out of order. When this occurs, we step back over previous feed items, then check their the item's main element has not been inserted into the DOM. It is the responsibility of this method to add the element to the DOM in any manner that it sees fit.
Parameters:
Name Type Description item
Object The item that is to be inserted.
col
Backbone.Collection A reference to the collection that this item was added to.
index
number The index in the collection to find the original item.
- Source:
- TickerView.js, line 196
-
scrollTo(contentId)
-
Sets the scrollLeft the TickerView such that the element containing the specified contentId aligns to the right of the current window.
Parameters:
Name Type Description contentId
number | string The id of the piece of content to scroll to.
- Source:
- TickerView.js, line 281
Returns:
The item that was scrolled to matching contentId
-
<protected, inner> initialize(opts)
-
Initializes a TickerView, and is called by backbone during view construction. Creates a couple of div's for styling and structure, then binds to the collection's add event.
Parameters:
Name Type Description opts
Object.<string, *> A set of options to configure this instance (@see constructor).
- Source:
- TickerView.js, line 31
-
<inner> render()
-
Renders a TickerView. Fades the view's holding element into view, and scrolls to the latest item.
- Source:
- TickerView.js, line 71


Subscription Plans
Be surprised with our unique features.
Free of all Ads
FEATURES:
Include free version features
Access to latest or upgraded features
DATA MANAGEMENT:
Access to latest or upgraded features
Buy only tools that you need
FEATURES:
Include all features in free version
Auto-finance management
Access to the online academy for learning materials and curriculum
Upload photos for sharing and safe keeping
Post videos to share
Request for a special feature
Have Ari on your application
APIs access
Access to latest or upgraded features
DATA MANAGEMENT:
Data retention for as long as you want


| X509V3.CNF(5) | File Formats Manual | X509V3.CNF(5) |
x509v3.cnf
—
Typically the application will contain an option to point to an extension section. Each line of the extension section takes the form:
critical
,]
extension_optionsIf critical
is present, then the extension
will be critical.
The format of extension_options depends on the value of extension_name.
There are four main types of extension: string extensions, multi-valued extensions, raw extensions, and arbitrary extensions.
String extensions simply have a string which contains either the value itself or how it is obtained. For example:
nsComment="This is a
Comment"
Multi-valued extensions have a short form and a long form. The short form is a list of names and values:
basicConstraints=critical,CA:true,pathlen:1
The long form allows the values to be placed in a separate section:
basicConstraints=critical,@bs_section [bs_section] CA=true pathlen=1
Both forms are equivalent.
The syntax of raw extensions is governed by the extension code: it can for example contain data in multiple sections. The correct syntax to use is defined by the extension code itself: check out the certificate policies extension for an example.
If an extension type is unsupported, then the arbitrary extension syntax must be used; see the ARBITRARY EXTENSIONS section for more details.
CA
followed
by TRUE
or FALSE
. If
CA
is TRUE
, then an optional
pathlen
name followed by a non-negative value can be
included. For example:
basicConstraints=CA:TRUE basicConstraints=CA:FALSE basicConstraints=critical,CA:TRUE, pathlen:0
A CA certificate must include the
basicConstraints
value with the
CA
field set to TRUE
. An end
user certificate must either set CA
to
FALSE
or exclude the extension entirely. Some
software may require the inclusion of
basicConstraints
with CA
set
to FALSE
for end entity certificates.
The pathlen
parameter indicates the
maximum number of CAs that can appear below this one in a chain. So if you
have a CA with a pathlen
of zero it can only be used
to sign end user certificates and not further CAs.
The supported names are: digitalSignature
,
nonRepudiation
,
keyEncipherment
,
dataEncipherment
,
keyAgreement
, keyCertSign
,
cRLSign
, encipherOnly
, and
decipherOnly
. Examples:
keyUsage=digitalSignature, nonRepudiation keyUsage=critical, keyCertSign
These can either be object short names or the dotted numerical form of OIDs. While any OID can be used, only certain values make sense. In particular the following PKIX, NS and MS values are meaningful:
| value | meaning |
serverAuth |
SSL/TLS web server authentication |
clientAuth |
SSL/TLS web client authentication |
codeSigning |
code signing |
emailProtection |
E-mail protection (S/MIME) |
timeStamping |
trusted timestamping |
OCSPSigning |
OCSP signing |
ipsecIKE |
IPsec internet key exchange |
msCodeInd |
Microsoft individual code signing (authenticode) |
msCodeCom |
Microsoft commercial code signing (authenticode) |
msCTLSign |
Microsoft trust list signing |
msEFS |
Microsoft encrypted file system |
Examples:
extendedKeyUsage=critical,codeSigning,<IP_ADDRESS> extendedKeyUsage=serverAuth,clientAuth
hash
which will automatically follow the
guidelines in RFC 3280 or a hex string giving the extension value to include.
The use of the hex string is strongly discouraged. Example:
subjectKeyIdentifier=hash
keyid
and issuer
: both can
take the optional value always
.
If the keyid
option is present, an attempt
is made to copy the subject key identifier from the parent certificate. If
the value always
is present, then an error is
returned if the option fails.
The issuer
option copies the issuer and
serial number from the issuer certificate. This will only be done if the
keyid
option fails or is not included unless the
always
flag will always include the value.
Example:
authorityKeyIdentifier=keyid,issuer
email
(an email address), URI
(a uniform resource indicator), DNS
(a DNS domain
name), RID
(a registered ID: OBJECT IDENTIFIER),
IP
(an IP address), dirName
(a
distinguished name), and otherName
.
The email
option can include a special
copy
value. This will automatically include any
email addresses contained in the certificate subject name in the
extension.
The IP address used in the IP
options can
be in either IPv4 or IPv6 format.
The value of dirName
should point to a
section containing the distinguished name to use as a set of name value
pairs. Multi values AVAs can be formed by prefacing the name with a
‘+
’ character.
otherName
can include arbitrary data
associated with an OID: the value should be the OID followed by a semicolon
and the content in standard
ASN1_generate_nconf(3)
format. Examples:
subjectAltName=email:copy,email:my@other.address,URI:http://my.url.here/ subjectAltName=IP:<IP_ADDRESS> subjectAltName=IP:13::17 subjectAltName=email:my@other.address,RID:<IP_ADDRESS> subjectAltName=otherName:<IP_ADDRESS>;UTF8:some other identifier subjectAltName=dirName:dir_sect [dir_sect] C=UK O=My Organization OU=My Unit CN=My Name
email
:copy
option because that
would not make sense. It does support an additional
issuer
:copy
option that will
copy all the subject alternative name values from the issuer certificate (if
possible). Example:
issuerAltName =
issuer:copy
email
:copy
is not
supported). accessOID can be any valid OID but only
certain values are meaningful, for example OCSP
and
caIssuers
. Example:
authorityInfoAccess = OCSP;URI:http://ocsp.my.host/ authorityInfoAccess = caIssuers;URI:http://my.ca/ca.html
For a name:value pair a new DistributionPoint with the fullName field set to the given value, both the cRLissuer and reasons fields are omitted in this case.
In the single option case, the section indicated contains values for each field. In this section:
If the name is fullname
, the value field
should contain the full name of the distribution point in the same format as
subject alternative name.
If the name is relativename
, then the
value field should contain a section name whose contents represent a DN
fragment to be placed in this field.
The name CRLIssuer
, if present, should
contain a value for this field in subject alternative name format.
If the name is reasons
, the value field
should consist of a comma separated field containing the reasons. Valid
reasons are: keyCompromise
,
CACompromise
,
affiliationChanged
,
superseded
,
cessationOfOperation
,
certificateHold
,
privilegeWithdrawn
, and
AACompromise
.
Simple examples:
crlDistributionPoints=URI:http://myhost.com/myca.crl crlDistributionPoints=URI:http://my.com/my.crl,URI:http://oth.com/my.crl
Full distribution point example:
crlDistributionPoints=crldp1_section [crldp1_section] fullname=URI:http://myhost.com/myca.crl CRLissuer=dirName:issuer_sect reasons=keyCompromise, CACompromise [issuer_sect] C=UK O=Organisation CN=Some Name
The names reasons
and
CRLissuer
are not recognized.
The name onlysomereasons
is accepted,
which sets this field. The value is in the same format as the CRL
distribution point reasons
field.
The names onlyuser
,
onlyCA
, onlyAA
, and
indirectCRL
are also accepted. The values should be
a boolean values (TRUE
or
FALSE
) to indicate the value of the corresponding
field. Example:
issuingDistributionPoint=critical, @idp_section [idp_section] fullname=URI:http://myhost.com/myca.crl indirectCRL=TRUE onlysomereasons=keyCompromise, CACompromise [issuer_sect] C=UK O=Organisation CN=Some Name
If you follow the PKIX recommendations and just use one OID, then you just include the value of that OID. Multiple OIDs can be set separated by commas, for example:
certificatePolicies= <IP_ADDRESS>,
<IP_ADDRESS>
If you wish to include qualifiers, then the policy OID and qualifiers need to be specified in a separate section: this is done by using the @section syntax instead of a literal OID value.
The section referred to must include the policy OID using the name
policyIdentifier
. CPSuri
qualifiers can be included using the syntax:
CPS
.nnn=valueuserNotice
qualifiers can be set using the
syntax:
userNotice
.nnn=@noticeThe value of the userNotice
qualifier is
specified in the relevant section. This section can include
explicitText
, organization
,
and noticeNumbers
options.
explicitText
and
organization
are text strings, and
noticeNumbers
is a comma separated list of numbers.
The organization
and
noticeNumbers
options (if included) must
both be present. If you use the
userNotice
option with IE5 then you need the
ia5org
option at the top level to modify the
encoding: otherwise it will not be interpreted properly. Example:
certificatePolicies=ia5org,<IP_ADDRESS>,<IP_ADDRESS>.8,@polsect [polsect] policyIdentifier = <IP_ADDRESS> CPS.1="http://my.host.name/" CPS.2="http://my.your.name/" userNotice.1=@notice [notice] explicitText="Explicit Text Here" organization="Organisation Name" noticeNumbers=1,2,3,4
The ia5org
option changes the type of the
organization
field. In RFC 2459, it can only be of
type DisplayText. In RFC 3280,
IA5String is also permissible. Some software (for
example some versions of MSIE) may require
ia5org
.
requireExplicitPolicy
or
inhibitPolicyMapping
and a non-negative integer value.
At least one component must be present. Example:
policyConstraints =
requireExplicitPolicy:3
inhibitAnyPolicy = 2
permitted
or
excluded
, followed by a semicolon. The rest of the
name and the value follows the syntax of subjectAltName except
email
:copy
is not supported
and the IP
form should consist of an IP addresses and
subnet mask separated by a slash. Examples:
nameConstraints=permitted;IP:<IP_ADDRESS>/<IP_ADDRESS> nameConstraints=permitted;email:.somedomain.com nameConstraints=excluded;email:.com
noCheck = ignored
The supported names are: status_request
and status_request_v2
. Example:
tlsfeature =
status_request
nsComment
) is a string extension
containing a comment which will be displayed when the certificate is viewed in
some browsers. Example:
nsComment = Some Random
Comment
Other supported extensions in this category are:
nsBaseUrl
, nsRevocationUrl
,
nsCaRevocationUrl
,
nsRenewalUrl
, nsCaPolicyUrl
,
and nsSslServerName
.
basicConstraints
,
keyUsage
, and extended key usage extensions are now
used instead.
Acceptable values for nsCertType
are:
client
, server
,
email
, objsign
,
reserved
, sslCA
,
emailCA
, objCA
.
There are two ways to encode arbitrary extensions.
The first way is to use the word ASN1
followed by the extension content using the same syntax as
ASN1_generate_nconf(3).
For example:
<IP_ADDRESS>=critical,ASN1:UTF8String:Some random data <IP_ADDRESS>=ASN1:SEQUENCE:seq_sect [seq_sect] field1 = UTF8:field1 field2 = UTF8:field2
It is also possible to use the word DER
to
include the raw encoded data in any extension.
<IP_ADDRESS>=critical,DER:01:02:03:04 <IP_ADDRESS>=DER:01020304
The value following DER
is a hex dump of
the DER encoding of the extension. Any extension can be placed in this form
to override the default behaviour. For example:
basicConstraints=critical,DER:00:01:02:03
The DER
and ASN1
options should be used with caution. It is possible to create totally
invalid extensions if they are not used carefully.
If an extension is multi-value and a field value must contain a comma, the long form must be used. Otherwise the comma would be misinterpreted as a field separator. For example,
subjectAltName=URI:ldap://somehost.com/CN=foo,OU=bar
will produce an error, but the following form is valid:
subjectAltName=@subject_alt_section [subject_alt_section] subjectAltName=URI:ldap://somehost.com/CN=foo,OU=bar
Due to the behaviour of the OpenSSL CONF library, the same field name can only occur once in a section. That means that
subjectAltName=@alt_section [alt_section] email=steve@here email=steve@there
will only use the last value. This can be worked around by using the form:
[alt_section] email.1=steve@here email.2=steve@there
| June 6, 2019 | Fidelix 0.2 |


There are many great ways to expand outside of your comfort zone without leaving the United States.
Top vacation destinations in the United States:
Mexico is easy to travel to by airplane and offers a wide variety of experiences, depending on your preferences.
Top vacation destinations in Mexico:
This is a great resource because they combine images and video. They provide a preview for the main article with a link to continue reading instead of filling the page with the whole article. This allows them to promote their other content. They also have a pop up window that invites the reader to sign up for their newsletter. The biggest downfall is that there are a lot of ads. However, they are balanced and do not obscure the content.


Java EE 7: Using JAX-RS Client API to consume RESTful Web Services
Overview
- Download and install the Java Platform, Enterprise Edition 7 (Java EE 7) software development kit from http://www.oracle.com/technetwork/java/javaee/downloads/index.html
- Download and install NetBeans integrated development environment (IDE) 7.3.1 from http://www.netbeans.org/downloads/index.html
- Download and install Oracle GlassFish Server 4.0 from http://www.oracle.com/technetwork/middleware/weblogic/downloads/index.html
- Knowledge of the Java programming language.
- Intermediate knowledge of Java EE 7.
- Basic knowledge of HTML.
Purpose
The purpose of this tutorial is to create a sticker story web application in which users can collaborate to create a story by dragging images into a book or canvas. When a sticker is dropped onto the canvas, it is rendered in all other web browsers that are connected to the server. A sticker's state is also persisted on the server so information is saved if a session ends.
Time to Complete
Approximately 1 hour
Scenario
You will start with a bare client interface and a minimal REST server. To complete the sticker story application, you'll use the JAX-RS 2.0 Client and JSON API to handle client-server communication. Finally, you'll persist the data in the server to for saving a sticker's current state.
Software Requirements
The following is a list of software requirements needed to accomplish this tutorial:
Prerequisites
Before starting this tutorial, you should have:
Introduction to JAX-RS 2.0 Clients
This section gives a brief introduction to Contexts and Dependency Injection, Servlets, and Enterprise JavaBeans.
Dependency Injection refers to the process of supplying an external dependency to a software component, allowing you to remove hard-coded dependencies. These dependencies can be supplied in a type-safe way and choose which implementation of a particular interface to use.
CDI injects components (such as Java beans) that live in well-defined references or scopes. This makes the use of components from different scopes more natural and convenient, since you can use and inject beans from different scopes. CDI is also integrated with Expression Language (EL), which allows any component to be used directly within a JavaServer Faces page or a JavaServer Pages page. CDI also helps you design and build loosely coupled systems, since it decouples the server and the client by means of well-defined types and qualifiers.
Preparing the Project
In this section, you create a Java EE 6 web application on which you’ll build the book registration application on.
The sticker-story and sticker-story-rest-server projects are running. You are now ready to start modifying them.
Generating a JSON List of Images
In this section, you learn how to generate a JSON list that contains the names of the sticker images that are available for the users to interact with. To accomplish this, you must modify the getImageList() method of the StickersResource class. Once the list of sticker names is generated, they can be accessed in the following URL: http://localhost:8080/sticker-story-rest-server/rest/stickers.
Retrieving the JSON List of Images
In this section, you retrieve the JSON list of sticker images generated in Section 3. To accomplish this, you modify the getAllStickers() method of the StickerSheet class.
A list of images is now obtained by the client.
Displaying the Images On the Client
In this section you learn how to display the sticker images in the web browser. Currently, images are served in the index.html file of the sticker-story project. The stickerContainer div contains the code that render the images by using JSF 2.0, calling the StickerServlet servlet, and sending the sticker name as a parameter, as shown in the following piece of code:
Note: To learn how JSF 2.0 is used to render the images, see the
To render the images on the browser, you will modify the StickerServlet class using JAX-RS 2.0 clients to make asynchronous calls to the server.
Creating an Asynchronous Request to the Server
Defining the Callback Function
Creating a Persistence Unit
- Create a client-side persistence request with the sticker’s data
- Sending the sticker’s data to all connected users
- Persist new sticker’s data
- A new client (or user) connects to the server.
- A sticker is dropped in the sticker board.
In this section, you learn how to persist the sticker’s information in the server. To accomplish this, you must:
Creating a Client-Side Persistence Request
In this section, you create a client-side persistence request. Client-side requests are made when one of the following events occur:
@OnMessage public void onMessage(Session session, Sticker sticker) { JsonObject jsonSticker = Json.createObjectBuilder() .add("name", sticker.getImage()) .add("x", sticker.getX()) .add("y", sticker.getY()) .build(); Client client = ClientBuilder.newClient(); client.target("http://localhost:8080/sticker-story-rest-server/rest/story") .request(); Set<Session> openSessions = session.getOpenSessions(); for (Session openSession : openSessions) { try { openSession.getBasicRemote().sendObject(sticker); } catch (IOException | EncodeException ex) { Logger.getLogger(StoryWebSocket.class.getName()).log(Level.SEVERE, null, ex); } } }
Sending the Persistence Request to the Server
When a new connection is made to the server, the onOpen() method is invoked. This method keeps a list of active sessions in the server. In this section, you learn how to request the list of active stickers when connecting to the server.
Persisting the Sticker Objects
In this section you process the HTTP POST and GET requests you defined in the previous sections.
Summary
- Use the Client class to build and execute requests for calling a REST service.
- Use the WebTarget class to specify a Client's target for requests.
- Build, process and manipulate JSON files.
- Model and create persistence requests.
- Send persistence requests to the server using HTTP POST.
- Request persistence requests from the server using HTTP GET.
- Receive JSON data and store it as objects in the server.
- Java API for JSON Processing
- JSR 339: JAX-RS 2.0: The Java API for RESTful Web Services
- Java EE 7 and JAX-RS 2.0
- JAX-RS Client API and GlassFish 4 - Logging HTTP messages
- Java EE 7: New Features.
- The Java EE 7 Tutorial
- The Java EE 7 Tutorial chapter on JSON Processing
- The Java EE 7 Tutorial chapter on Building RESTful Web Services With JAX-RS
- Oracle Online Learning Library ">Oracle Online Learning Library - Java Resources
- To learn more about Java EE 7, refer to additional OBEs in the Oracle Learning Library.
- Lead Curriculum Developer: Miguel Salazar
- Other Contributors: Eduardo Moranchel
In this tutorial you learned how to use the Java API for RESTful Web Services (JAX-RS 2.0) and the Java API for JSON Processing to build an interactive web application that persists an object's properties in the server.
You also learned how to:
Resources
For more information about the topics in this tutorial, see:
Credits
To help navigate this Oracle by Example, note the following:
- Hiding Header Buttons:
- Click the Title to hide the buttons in the header. To show the buttons again, simply click the Title again.
- Topic List Button:
- A list of all the topics. Click one of the topics to navigate to that section.
- Expand/Collapse All Topics:
- To show/hide all the detail for all the sections. By default, all topics are collapsed
- Show/Hide All Images:
- To show/hide all the screenshots. By default, all images are displayed.
- Print:
- To print the content. The content currently displayed or hidden will be printed.
To navigate to a particular section in this tutorial, select the topic from the list.


{{ item.score }} edges from {{modality.value}}
{{ item.score }} edges from other modalities
{{ item.score }} edges to {{modality.value}}
{{ item.score }} edges to other modalities
{{ item.score }} edges with {{modality.value}}
{{ item.score }} edges with other modalities
{{ item.score }} edges from {{modality.value}}
{{ item.score }} edges to {{modality.value}}
{{ item.score }} edges with {{modality.value}}


| Address | Token name | Amount |
|---|---|---|
| {{account['name']}} | ||
| {{key}} | {{value}} | {% end %} {% end %}
This data is taken from the local Bismuth blockchain ledger. Transactions need to be processed by your local Bismuth node before they make changes to balances here. Shielded tokens do not operate on notion of time, therefore in default implementation, block numbers and transaction times are omitted during processing. Updates here happen on page refresh.


Risk Profile: Moderate
- Stocks
- Large Cap Blend 20% {{am*0.2}}
- Mid Cap Blend 20% {{am*0.2}}
- Small Cap Blend 10% {{am*0.1}}
- Emerging Markets 10% {{am*0.1}}
- Corporate Bonds 25% {{am*0.25}}
- Fd’s 5% {{am*0.05}}
- Mutual funds 10% {{am*0.1}}
- looking for a balance between portfolio stability and portfolio appreciation
- willing and able to accept a moderate level of risk and return
- an investor focused on growth but looking for greater diversification
- someone with a portfolio that primarily includes a balance of investments in bonds and equities


about me
irankundaFabrice
Fabrice is a full stacker web developer and mobile app developer, I’m a strong believer in using research and testing to enhance my problem solving skills because I’ve seen it make a world of a difference! I enjoy working with people who are in different fields as mine! (yes it’s true!) in cross functional teams because different perspective leads to a well rounded solution.
Read more →mobile app
- Python
- Java
backend
- Nodejs/Express js
- Python/Django
- MongoDB & SQLlite
frontend
- HTML5,CSS3 & Bootstrap
- JavaScript/Jquery
- React.js


Vision Portfolio Management Application Layer: Data Feeds
| Application Feeds |
Data Feed: CompanyToCountry
Category: MembershipFeed
Summary:
Available Fields:
| Field | Type | Description
|
|---|
| --- Required Fields ---
|
|---|
| groupId
| String
| id of existing Country instance
|
| memberId
| String
| id of existing Company instance
|
Special Processing Rules:
- The groupId and memberId fields must be supplied.
The groupId must correspond to an existing Country
instance. The memberId must correspond to
an existing Company instance.
- The country property at Company
will be updated with the Country
indicated by the supplied groupId.
The memberList property at Country
will be updated for each Country affected by this feed.
- To indicate that the company no longer
has a country (if the company is acquired for example), use
the string Default as the value of groupId field.
- This feed is designed as an append-style update. You
only need to supply records that assign initial country values
or that change existing ones.
- If a country is assigned to a company that does not have a
value for its base currency, the base currency associated with
the country is assigned to the company's baseCurrency
property.
Related Feeds:
Sample Upload:
The following tab-delimited feed could be used to define company-country membership
over time.
Interface ExternalFeedManager upload: "CompanyToCountry" using:
"memberId groupId
00036110 US
00079410 US
00194110 CA
00443110 MX
01310410 US
01371610 CA
" ;
| Copyright © 1998 Innovative Systems Techniques, Inc.
| Updated August 27, 1998
|


com
.
lucidworks
.
spark
.
query
SolrTermVector
Related Doc:
package query
class
SolrTermVector
extends
SparseVector
with
Vector
with
Serializable
Linear Supertypes
SparseVector
,
Vector
,
Serializable
,
Serializable
,
AnyRef
,
Any
Ordering
Alphabetic
By Inheritance
Inherited
SolrTermVector
SparseVector
Vector
Serializable
Serializable
AnyRef
Any
Hide All
Show All
Visibility
Public
All
Instance Constructors
new
SolrTermVector
(
docId:
String
,
terms:
Array
[
String
]
,
size:
Int
,
indices:
Array
[
Int
]
,
weights:
Array
[
Double
]
)
Attributes
protected[
com.lucidworks.spark.query
]
Value Members
final
def
!=
(
arg0:
Any
)
:
Boolean
Definition Classes
AnyRef → Any
final
def
##
()
:
Int
Definition Classes
AnyRef → Any
final
def
==
(
arg0:
Any
)
:
Boolean
Definition Classes
AnyRef → Any
def
apply
(
i:
Int
)
:
Double
Definition Classes
Vector
Annotations
@Since
(
"1.1.0"
)
def
argmax
:
Int
Definition Classes
SparseVector → Vector
Annotations
@Since
(
"1.5.0"
)
final
def
asInstanceOf
[
T0
]
:
T0
Definition Classes
Any
def
asML
:
SparseVector
Definition Classes
SparseVector → Vector
Annotations
@Since
(
"2.0.0"
)
def
clone
()
:
AnyRef
Attributes
protected[
java.lang
]
Definition Classes
AnyRef
Annotations
@throws
(
...
)
def
compressed
:
Vector
Definition Classes
Vector
Annotations
@Since
(
"1.4.0"
)
def
copy
:
SparseVector
Definition Classes
SparseVector → Vector
Annotations
@Since
(
"1.1.0"
)
final
def
eq
(
arg0:
AnyRef
)
:
Boolean
Definition Classes
AnyRef
def
equals
(
other:
Any
)
:
Boolean
Definition Classes
SparseVector → Vector → AnyRef → Any
def
finalize
()
:
Unit
Attributes
protected[
java.lang
]
Definition Classes
AnyRef
Annotations
@throws
(
classOf[java.lang.Throwable]
)
def
foreachActive
(
f: (
Int
,
Double
) ⇒
Unit
)
:
Unit
Definition Classes
SparseVector → Vector
Annotations
@Since
(
"1.6.0"
)
final
def
getClass
()
:
Class
[_]
Definition Classes
AnyRef → Any
def
getDocumentId
()
:
String
def
hashCode
()
:
Int
Definition Classes
SparseVector → Vector → AnyRef → Any
val
indices
:
Array
[
Int
]
Definition Classes
SparseVector
Annotations
@Since
(
"1.0.0"
)
final
def
isInstanceOf
[
T0
]
:
Boolean
Definition Classes
Any
final
def
ne
(
arg0:
AnyRef
)
:
Boolean
Definition Classes
AnyRef
final
def
notify
()
:
Unit
Definition Classes
AnyRef
final
def
notifyAll
()
:
Unit
Definition Classes
AnyRef
def
numActives
:
Int
Definition Classes
SparseVector → Vector
Annotations
@Since
(
"1.4.0"
)
def
numNonzeros
:
Int
Definition Classes
SparseVector → Vector
Annotations
@Since
(
"1.4.0"
)
val
size
:
Int
Definition Classes
SparseVector → Vector
Annotations
@Since
(
"1.0.0"
)
final
def
synchronized
[
T0
]
(
arg0: ⇒
T0
)
:
T0
Definition Classes
AnyRef
def
toArray
:
Array
[
Double
]
Definition Classes
SparseVector → Vector
Annotations
@Since
(
"1.0.0"
)
def
toDense
:
DenseVector
Definition Classes
Vector
Annotations
@Since
(
"1.4.0"
)
def
toJson
:
String
Definition Classes
SparseVector → Vector
Annotations
@Since
(
"1.6.0"
)
def
toSparse
:
SparseVector
Definition Classes
SparseVector → Vector
Annotations
@Since
(
"1.4.0"
)
def
toString
()
:
String
Definition Classes
SolrTermVector
→ SparseVector → AnyRef → Any
val
values
:
Array
[
Double
]
Definition Classes
SparseVector
Annotations
@Since
(
"1.0.0"
)
final
def
wait
()
:
Unit
Definition Classes
AnyRef
Annotations
@throws
(
...
)
final
def
wait
(
arg0:
Long
,
arg1:
Int
)
:
Unit
Definition Classes
AnyRef
Annotations
@throws
(
...
)
final
def
wait
(
arg0:
Long
)
:
Unit
Definition Classes
AnyRef
Annotations
@throws
(
...
)
Inherited from
SparseVector
Inherited from
Vector
Inherited from
Serializable
Inherited from
Serializable
Inherited from
AnyRef
Inherited from
Any
Ungrouped