Datasets:

BramVanroy

/

stack_md_lid

like 4

f77cccca8959eb07be25a115ac67aba8fdc553d0

md

Markdown

README.md

JiaqiZengr/JiaqiZengr.github.io

29e2912ed32392f7df2d8da7367afcd9322b5107

README.md

JiaqiZengr/JiaqiZengr.github.io

29e2912ed32392f7df2d8da7367afcd9322b5107

README.md

JiaqiZengr/JiaqiZengr.github.io

29e2912ed32392f7df2d8da7367afcd9322b5107

# Welcome to Jiaqi's space * [Data Analysis - Jiaqi Zeng](https://jiaqizengr.github.io/categories/#Data%20Analysis-ref)

kor_Hang

f77d53e47e1fe556ade6c829149f78e07746c71d

md

Markdown

pages.zh_CN/common/fold.md

zero-MK/tldr

df6dd348b31f6ad9d7a10e450cb4de31b3e1f586

pages.zh_CN/common/fold.md

zero-MK/tldr

df6dd348b31f6ad9d7a10e450cb4de31b3e1f586

pages.zh_CN/common/fold.md

zero-MK/tldr

df6dd348b31f6ad9d7a10e450cb4de31b3e1f586

2020-07-26T16:51:50.000Z

2020-08-18T07:06:49.000Z

# fold > 包装输入文件中的每一行以适合指定的宽度并将其打印到标准输出 > 5 包裹 ): - 将每一行换行为默认宽度（80个字符）： `fold {{file}}` - 将每一行包裹到宽度 30 ： `fold -w30 {{file}}` - 将每一行换行为宽度 5 并在空格处打破该行（将每个空格分隔的单词放在一个新行中，包含长度 > 5 的单词）： `fold -w5 -s {{file}}` [#]: contributors: ([潘潘])

yue_Hant

f78003c6620adecd3e8930c69e72ca9cd7b02dfc

md

Markdown

README.md

atjn/eslint-config

0c7060e58ee4b4b4bc45709497fab4b8d8386f2c

README.md

atjn/eslint-config

0c7060e58ee4b4b4bc45709497fab4b8d8386f2c

2021-05-11T23:53:12.000Z

2021-12-29T10:43:59.000Z

README.md

atjn/eslint-config

0c7060e58ee4b4b4bc45709497fab4b8d8386f2c

# My personal JavaScript code style [](https://www.npmjs.com/package/@atjn/eslint-config) [](https://www.npmjs.com/package/@atjn/eslint-config?activeTab=dependencies) [](https://github.com/atjn/eslint-config/actions/workflows/code-quality.yml) [](https://lgtm.com/projects/g/atjn/eslint-config/context:javascript) This is my personal JavaScript code style, defined as an [ESLint](https://eslint.org/) shareable configuration. My style is: ### Secure By enforcing best practices, my code becomes much more secure and stable. ### Loosely styled I have a loosely defined coding style which helps make the code more consistent and readable. I purposefully don't get too specific with small details because I often find that slightly varying my code style can help me write more efficient and readable code. ### Documented By requiring JSDoc comments for all files and functions, it becomes much easier to read through and understand my code.

eng_Latn

f7800ad234e85991fd326fa38ab34301e7757165

md

Markdown

2021.2/Readme.md

isabella232/whatsnewingoland

5847b02b7ae077564ddfe7ddd99b8cb247fefb88

2021-03-23T02:58:41.000Z

2022-03-19T04:27:07.000Z

2021.2/Readme.md

dlsniper/whatsnewingoland

5847b02b7ae077564ddfe7ddd99b8cb247fefb88

2021-04-15T15:03:01.000Z

2022-01-11T08:34:10.000Z

2021.2/Readme.md

isabella232/whatsnewingoland

5847b02b7ae077564ddfe7ddd99b8cb247fefb88

2021-03-26T16:51:54.000Z

2022-03-19T08:57:07.000Z

# What's New In 2021.2 This is a collection of new features in GoLand 2021.2. Some of these are listed here, some have their own separate demo, for the convenience of showing the feature itself. - [Go 1.17 support](#go-117-support) - [Run gofmt after the builtin formatter](#run-gofmt-after-the-builtin-formatter) - [Go modules support](#go-modules-support) - [Load go.mod changes manually](#load-gomod-changes-manually) - [Better handling of Go versions from go.mod files](#better-handling-of-go-versions-from-gomod-files) - [Unused dependency in go.mod inspection](#unused-dependency-in-gomod-inspection) - [Better view of attached projects](#better-view-of-attached-projects) - [Web Features](#web-features) - [Browser pages reload on save](#browser-pages-reload-on-save) - [Completion for parameter types based on function calls](#completion-for-parameter-types-based-on-function-calls) - [New arrow function live template](#new-arrow-function-live-template) - [Code completion for private npm packages](#code-completion-for-private-npm-packages) - [Support for TypeScript types in JSDoc](#support-for-typescript-types-in-jsdoc) - [Support for web-types](#support-for-web-types) - [React support](#react-support) - [Rename refactoring for React useState hooks](#rename-refactoring-for-react-usestate-hooks) - [Support for classnames and clsx libraries](#support-for-classnames-and-clsx-libraries) - [Version Control](#version-control) - [Sign commit with GPG](#sign-commit-with-gpg) - [Run custom Tests before commit](#run-custom-tests-before-commit) - [Run custom Inspections before commit](#run-custom-inspections-before-commit) - [Run custom Cleanup inspections before commit](#run-custom-cleanup-inspections-before-commit) - [Docker](#docker) - [Quick documentation for keys in Dockerfiles and docker-compose.yaml files](#quick-documentation-for-keys-in-dockerfiles-and-docker-composeyaml-files) - [Restart/pause/unpause containers](#restartpauseunpause-containers) - [Docker Compose](#docker-compose) - [Inspection for ports mapping type in docker-compose](#inspection-for-ports-mapping-type-in-docker-compose) - [Support for operations on multiple services/containers](#support-for-operations-on-multiple-servicescontainers) - [Inspection for shm_size key values](#inspection-for-shm_size-key-values) - [Inspection for device_cgroup_rules values](#inspection-for-device_cgroup_rules-values) - [Kubernetes](#kubernetes) - [Configure custom namespaces manually](#configure-custom-namespaces-manually) - [Platform](#platform) - [Accessibility](#accessibility) - [Actions on save](#actions-on-save) - [Improvements for the Settings/Preferences dialog](#improvements-for-the-settingspreferences-dialog) - [Automatic cache and logs cleanup](#automatic-cache-and-logs-cleanup) - [Search for text in the Local History](#search-for-text-in-the-local-history) - [New Terminal options](#new-terminal-options) - [Select the shell of a new Terminal](#select-the-shell-of-a-new-terminal) - [Better project icon](#better-project-icon) - [Preview files when debugging](#preview-files-when-debugging) - [New Scratch File from selection](#new-scratch-file-from-selection) - [Remove Scratch File when closing it](#remove-scratch-file-when-closing-it) If you want, you can watch a recording of the presentation based on this content: [](https://www.youtube.com/watch?v=4JAmpWdPe-k "What's New in GoLand 2021.2") ## Go 1.17 support 01. Convert a slice to an array pointer Go 1.17 brings a new language change: > Converting a slice to an array pointer yields a pointer to the underlying array of the slice. If the length of the slice is less than the length of the array, a run-time panic occurs. Source: [Go 1.17 release notes](https://tip.golang.org/ref/spec#Conversions_from_slice_to_array_pointer). [Demo](01%20-%20convert%20slice%20to%20array%20pointer/main.go) ## Run gofmt after the builtin formatter 02. If you want to run gofmt, you can now do it in a fourth way: as a step after the builtin formatter. To use this feature, check the `On code reformat` option under `Settings/Preferences | Editor | Code Style | Go | Other`. Now you can use the default shortcut, `Ctrl + Alt + L` on Windows/Linux or `Cmd + Alt + L` on macOS, to trigger the builtin formatter. **Pro tip**: You can also search for `Run gofmt` in the IDE `Settings/Preferences`, and activate the option as described above.  ## Go modules support ### Load go.mod changes manually 03. Up until now, changes in the go.mod file where automatically detected. However, this could lead to situations where the update was triggered before a user could finish typing everything needed. Additionally, some users told us they prefer to launch the update process manually. We listened to this feedback and implemented a new way to manually trigger the updates after editing a go.mod file. To use it, navigate to `Settings/Preferences | Build, Execution, Deployment | Build Tools` and select `External changes` instead of `Any changes`.  After this, you'll see a new option appearing on the top right of the editor after making any changes in the file.  [Demo](03%20-%20load%20go%20mod%20changes%20manually/go.mod) ### Better handling of Go versions from go.mod files 04. Until now, the version Go SDK used in the project was the one that GoLand took into account when performing inspections or other tasks. However, this is not always correct, as the `go` directive in the `go.mod` file might specify a different version. That's why, since this release, GoLand supports looking at the Go version from `go.mod` files rather than just the project SDK. [Demo](04%20-%20better%20handling%20of%20go%20version%20from%20go%20mod%20files/main.go) ## Unused dependency in go.mod inspection 05. You can now determine the unused module dependencies in `go.mod` files thanks to a new inspection that marks them with a grey color. [Demo](05%20-%20unused%20dependendencies%20in%20gomod%20files/go.mod) ## Better view of attached projects 06. Working with multiple projects at the same time is now cleaner thanks to the improved display of attached projects. To attach a project to an existing one, use the Open command and select the "Attach" option in the follow-up dialog.  After this, you can work with the new project alongside the existing one.  When you finish with the attached project, you can detach it using the `right-click | Remove from Project View` action.  ## Web Features ### Browser pages reload on save 07. The IDE can automatically reload the page opened in a browser after you make changes to an HTML file, or the linked CSS and JavaScript files. Reloading is triggered whenever changes are saved in the IDE, either automatically or using _Ctrl + S on Windows/Linux_ or _Cmd + S on macOS_, or when changes are made to a file externally. To use this, open the file from the IDE via the icon on the upper right-side of the editor or via `View | Open in Browser | <browser name>`. [Demo](07%20-%20automatic%20browser%20files%20reload/index.html) ### Completion for parameter types based on function calls 08. The IDE will show you completion suggestions based on the type used in the function call for the parameters in the function body. [Demo](08%20-%20js%20completion%20for%20parameter%20types%20based%20on%20function%20calls/demo.js) **Pro tip:** Use the Smart Type Completion to narrow-down the list further. ### New arrow function Live Template 09. Writing a new arrow function is now even faster thanks to the new `arf` Live Template. [Demo](09%20-%20new%20arrow%20function%20live%20template/demo.js) ### Code completion for private npm packages 10. Code completion now works for private npm packages in `package.json` files. The IDE will let you browse information about the latest versions of the package, similarly to the public packages. ### Support for TypeScript types in JSDoc 11. You can now use the TypeScript syntax within JSDoc comments in .js files. [Demo](11%20-%20typescript%20type%20references%20in%20jsdoc/ref.js) ### Support for web-types 12. Web-types is an open source standard for documenting various web frameworks. It's framework-agnostic and provides IDEs and other tools with metadata information about contents of a web components library. Web-types are developed by JetBrains and work on this format started a few months prior to this release. You might already see the effects of this when using the Vue.js plugin. To learn more about web-types, check out [this article](https://blog.jetbrains.com/webstorm/2021/01/web-types/). ### React support #### Rename refactoring for React useState hooks 13. When using the `Rename refactoring`, Shift + F6 on Windows/Linux or ⇧ + F6 on macOS, you it will detect if you are using useStates from React and rename both values at once. [Demo](13%20-%20rename%20refactoring%20for%20react%20usestate%20hooks/demo.js) #### Support for classnames and clsx libraries 14. When using the `classnames` and `clsx` libraries, the IDE will show completion suggestions for your CSS classes and resolve all symbols in string literals and properties with literal names. [Demo](14%20-%20support%20for%20classnames%20and%20clsx%20libraries/demo.js) ## Version Control ### Sign commit with GPG 15. Signing a commit with a GPG key is now possible. After configuring the git client with the correct key, head over to `Settings/Preferences | Version Control | Git` and ensure that the option `Configure GPG Key...` is turned on and points to the expected key.  ### Run custom Tests before commit 16. You can now configure a test to run before committing your files. Invoke the Commit feature using Ctrl + K on Windows/Linux and Cmd + K on macOS, then select the `Commit options` and check the `Run Tests` option and select which run configuration you wish to run. **Note:** You must have the `Use non-modal commit interface` activated before you can use this feature. Check your settings under `Settings/Preferences | Version Control | Commit`.  **Pro-tip:** You can use the [Compound configuration type](https://www.jetbrains.com/help/go/run-debug-configuration.html#compound-configs) to run more than a single run configuration. [Demo](16%20-%20run%20tests%20before%20commit/main_test.go) ### Run custom Inspections before commit 17. Committing error-free code reduces the time it takes for reviews to go happen and makes everyone happy. Since not all errors may be caught by tests, you can choose to run Inspections before a commit. This will improve your chances to have fewer bugs in code. To use this feature, invoke the `Commit` feature, then select the `Analyze code` feature.  ### Run custom Cleanup inspections before commit 18. Tests and Inspections are not the only features that you can run before a commit. You can also trigger an automatic code cleanup, using the `Cleanup` feature from the commit dialog.  ## Docker ### Quick documentation for keys in Dockerfiles and docker-compose.yaml files 19. Dockerfile and docker-compose.yaml files now support displaying documentation references via the Quick Documentation, Ctrl + Q on Windows/Linux or F1 on macOS. [Demo](19%20-%20docker%20quick%20documentation/Dockerfile) ### Restart/pause/unpause containers 20. Containers can now be paused/resumed or restarted from the Services view. [Demo](20%20-%20docker%20pause%20container) ### Docker Compose #### Inspection for ports mapping type in docker-compose 21. A new inspection checks if the ports mapping in docker-compose.yaml files is correct. [Demo](21%20-%20docker-compose%20ports%20mapping%20validation/docker-compose.yaml) #### Support for operations on multiple services/containers 22. You can now select multiple containers or Docker Compose Services from the Services view, Alt + 8 on Windows/Linux or Cmd + 8 on macOS, and perform common operations, such as start, stop, restart, pause, or delete on them. [Demo](22%20-%20docker-compose%20handle%20multiple%20containers/docker-compose.yaml) #### Inspection for shm_size key values 23. A new inspection for docker-compose files will tell you when the `shm_size` values are incorrect. [Demo](23%20-%20docker-shm-size-inspection/docker-compose.yaml) #### Inspection for device_cgroup_rules values 24. When using device_cgroup_rules, the value types are now correctly inspected, and the IDE will inform you if you are not using a string, or a list of strings. [Demo](24%20-%20docker-device-cgroup-rules-inspection/docker-compose.yaml) ## Kubernetes ### Configure custom namespaces manually 25. If the plugin cannot automatically infer the available Kubernetes namespaces, now you can configure them manually. This will solve the problem when the user does not have the required permissions to perform namespace listing. To use this feature, head over to `Settings/Preferences | Build, Execution, Deployment | Kubernetes` and configure the namespace in the corresponding section.  ## Platform ### Accessibility 26. We reduced the number of screen read help tooltips. A list of code completion options will be read out loud on macOS. The content of the selected combo box and combo box lists was added too. The results in Search Everywhere are now properly pronounced. ### Actions on save 27. It's now possible to trigger various IDE actions on save. Before, you could use File Watchers to achieve a part of this functionality, but IDE actions such as Optimize Imports, or using the builtin code formatter were not possible. Starting with 2021.2, you can turn on such actions under `Settings/Preferences | Tools | Actions on Save`.  ### Improvements for the Settings/Preferences dialog 28. We added a new node called `Advanced Settings` in `Settings/Preferences` dialog. Most of the options there were transferred from the `Registry...` as we wanted to make those options easier to access. You'll also find some new configuration options there, such as the ability to set a left margin in `Distraction-free mode`.  ### Automatic cache and logs cleanup 29. The IDE will automatically clean up any cache and log directories that were last updated more than 180 days ago. The system settings and plugins directories will stay intact. To trigger this process manually, go to `Help | Delete Leftover IDE Directories...`.  ### Search for text in the Local History 30. With the new Search field to the `Local History` dialog you quickly get to the necessary text in your revisions. To invoke it, press the `Find` shortcut, Ctrl + F on Windows/Linux or Cmd + F on macOS.  ### New Terminal options 31. You can now select the cursor shape in the builtin Terminal. And, if you are using macOS, you can now use `Option as Meta key`, similar to the same-name option in the native Terminal on macOS. This allows the `⌥` key on the keyboard to act as a meta modifier that can be used in combination with other keys instead of just as an Escape key. For example, you can use the following shortcuts: ⌥ + F – go to the next word ⌥ + B – go back a word ⌥ + D – delete the next word You can tick the checkboxes for the new options in Settings/Preferences | Tools | Terminal.  ### Select the shell of a new Terminal 32. Up until now, you could configure which shell you want to use only from the `Settings/Preferences | Tools | Terminal`. Since this was not flexible enough, we introduced a new way to create new Terminal tabs. Click on the `⋁` button next to the existing tabs and select which shell to use. You can also create a new SSH session from it, if you have any servers configured or configure a new one.  ### Better project icon 33. You can add a project icon to the project from the projects list on the Welcome screen. Upload custom icons by right-clicking on any project and select `Choose Project Icon...` from the context menu.  ### Preview files when debugging 34. The `Preview tab` was extended to work with the files that open during debugging. To activate this feature, navigate to `Settings/Preferences | Editor | General | Editor Tabs`. When using this feature, you'll be able to preview files without worrying about creating a new tab/closing them after/losing your existing tabs. ### New Scratch File from selection 35. You can now select some code, press Alt+Enter on Windows/Linux or ⌥ + ⏎ on macOS, and then choose `Create new scratch file from selection` to quickly create a new scratch containing the same code. ### Remove Scratch File when closing it 36. When you close an empty scratch file, it will automatically be removed.

eng_Latn

f780ae76e3651f8ec763b91249d2b1a17e3b8fe3

md

Markdown

_posts/2020-03-25-thingivers.md

pipiscrew/pipiscrew.github.io

9d81bd323c800a1bff2b6d26c3ec3eb96fb41004

_posts/2020-03-25-thingivers.md

pipiscrew/pipiscrew.github.io

9d81bd323c800a1bff2b6d26c3ec3eb96fb41004

_posts/2020-03-25-thingivers.md

pipiscrew/pipiscrew.github.io

9d81bd323c800a1bff2b6d26c3ec3eb96fb41004

--- title: Thingiverse - Digital Designs for Physical Objects author: PipisCrew date: 2020-03-25 categories: [news] toc: true --- https://www.thingiverse.com/ #3dprint origin - https://www.pipiscrew.com/?p=17661 thingiverse-digital-designs-for-physical-objects

yue_Hant

f780d1d017cc3013aafc9944c5fddc3fa6f70594

md

Markdown

README.md

svetlana-rezvaya/go-machine

dd5fa78df7c72a6129c819b7d36fc8e47bd692ce

README.md

svetlana-rezvaya/go-machine

dd5fa78df7c72a6129c819b7d36fc8e47bd692ce

README.md

svetlana-rezvaya/go-machine

dd5fa78df7c72a6129c819b7d36fc8e47bd692ce

# go-machine [](https://godoc.org/github.com/svetlana-rezvaya/go-machine) [](https://goreportcard.com/report/github.com/svetlana-rezvaya/go-machine) [](https://app.travis-ci.com/svetlana-rezvaya/go-machine) [](https://codecov.io/gh/svetlana-rezvaya/go-machine) The library implementing a simple virtual machine. ## Instruction Set [Instruction Set](docs/) ## Installation ``` $ go get github.com/svetlana-rezvaya/go-machine ``` ## Usage Example ```go package main import ( "fmt" "log" "github.com/svetlana-rezvaya/go-machine" ) func isPrime(number int) (bool, error) { const ( inputRegisterIndex = iota outputRegisterIndex utilityRegisterIndex counterRegisterIndex ipRegisterIndex registerCount ) const ( loopIterationLabel = iota*100 + 100 successLabel failureLabel finishLabel ) const ( successMark = iota + 1 failureMark ) program := []int{ // load the input machine.LoadConstantOpcode, number, inputRegisterIndex, // compare the input with 2 machine.LoadConstantOpcode, 2, utilityRegisterIndex, machine.SubtractionOpcode, inputRegisterIndex, utilityRegisterIndex, utilityRegisterIndex, machine.JumpIfNegativeOpcode, utilityRegisterIndex, failureLabel, machine.JumpIfZeroOpcode, utilityRegisterIndex, successLabel, // start the check loop // initialize the counter machine.LoadConstantOpcode, 2, counterRegisterIndex, machine.JumpOpcode, loopIterationLabel, // check the loop break condition: the counter should be less than the input loopIterationLabel: machine.SubtractionOpcode, inputRegisterIndex, counterRegisterIndex, utilityRegisterIndex, machine.JumpIfNegativeOpcode, utilityRegisterIndex, successLabel, machine.JumpIfZeroOpcode, utilityRegisterIndex, successLabel, // check divisibility of the input by the counter machine.ModuloOpcode, inputRegisterIndex, counterRegisterIndex, utilityRegisterIndex, machine.JumpIfZeroOpcode, utilityRegisterIndex, failureLabel, // increase the counter machine.LoadConstantOpcode, 1, utilityRegisterIndex, machine.AdditionOpcode, counterRegisterIndex, utilityRegisterIndex, counterRegisterIndex, // go to the next iteration machine.JumpOpcode, loopIterationLabel, // set the output to success successLabel: machine.LoadConstantOpcode, successMark, outputRegisterIndex, machine.JumpOpcode, finishLabel, // set the output to failure failureLabel: machine.LoadConstantOpcode, failureMark, outputRegisterIndex, machine.JumpOpcode, finishLabel, // no operation finishLabel: machine.JumpOpcode, finishLabel + 2, } machineInstance := machine.Machine{ Memory: program, Registers: make([]int, registerCount), IPRegisterIndex: ipRegisterIndex, } err := machine.ExecuteMachine(machineInstance) if err != nil { return false, fmt.Errorf("unable to execute the machine: %s", err) } isSuccessful := machineInstance.Registers[outputRegisterIndex] == successMark return isSuccessful, nil } func main() { for number := 0; number < 100; number++ { isSuccessful, err := isPrime(number) if err != nil { log.Fatalf("unable to check primality of number %d: %s", number, err) } if isSuccessful { fmt.Printf("number %d is prime\n", number) } } // Output: // number 2 is prime // number 3 is prime // number 5 is prime // number 7 is prime // number 11 is prime // number 13 is prime // number 17 is prime // number 19 is prime // number 23 is prime // number 29 is prime // number 31 is prime // number 37 is prime // number 41 is prime // number 43 is prime // number 47 is prime // number 53 is prime // number 59 is prime // number 61 is prime // number 67 is prime // number 71 is prime // number 73 is prime // number 79 is prime // number 83 is prime // number 89 is prime // number 97 is prime } ``` ## License The MIT License (MIT) Copyright &copy; 2021 svetlana-rezvaya

eng_Latn

f7830f9ff60d23230eba78bd11e04226c346fc83

md

Markdown

5/README.md

pjwilliams2/project-euler

c1a8c0d7e2cb50a4c4ce5cf494f895037e0c02ec

5/README.md

pjwilliams2/project-euler

c1a8c0d7e2cb50a4c4ce5cf494f895037e0c02ec

5/README.md

pjwilliams2/project-euler

c1a8c0d7e2cb50a4c4ce5cf494f895037e0c02ec

# Project Euler Problem 5 [Problem 5][link] [link]: https://projecteuler.net/problem=5 "Problem 5"

deu_Latn

f78372def1ef39a3a9365522586303e85fdce4e2

md

Markdown

README.md

Luukuton/qupath-edu-cloud

0577cd92669dcb7627a4b3fa41922e5c60414257

README.md

Luukuton/qupath-edu-cloud

0577cd92669dcb7627a4b3fa41922e5c60414257

2022-03-28T06:00:23.000Z

2022-03-28T06:00:23.000Z

README.md

Luukuton/qupath-edu-cloud

0577cd92669dcb7627a4b3fa41922e5c60414257

# QuPath Edu Cloud [](https://rare.fi/) ## Instructions - Copy .env.example as .env and change `REACT_APP_SERVERS_URL`. - Install latest supported nodejs and npm (specified in [package.json](package.json)) - Run `npm i` and `npm start`

eng_Latn

f786f683e425153ab1984342a1bdfd4a874c7e1e

md

Markdown

README.md

ordinary-developer/book_qt_5_3_m_shlee

9e760323ef8ecd32fb0ef775a8633f8021da972c

README.md

ordinary-developer/book_qt_5_3_m_shlee

9e760323ef8ecd32fb0ef775a8633f8021da972c

README.md

ordinary-developer/book_qt_5_3_m_shlee

9e760323ef8ecd32fb0ef775a8633f8021da972c

Project information ------------------- This repository contains my files (my code snippets and my synopses about the main book's topics) for the book **"Qt 5.3"** by **Maks Shlee**. [here is the link to it's site](http://www.ozon.ru/context/detail/id/31619787/). Installation ------------ simply copy (clone the repository) and see and read it Basic usage ----------- `$ git clone https://gitlab.com/book_synopses_and_code_samples/qt_5_3_m_shlee.git` or `$ git clone https://github.com/ordinary-developer/book_qt_5_3_m_shlee.git` License ------- This project is offered under the MIT license. Contributing ------------ This project doesn't need to be contributed. But just in case you can always connect with me.

eng_Latn

f787d34d5994daaf996e5aaea6ddc18c1178fb22

md

Markdown

ros/README.md

RTSYork/rtscar

134f2e6aaa420fbaa4f22241561b74ef4df3a1aa

ros/README.md

RTSYork/rtscar

134f2e6aaa420fbaa4f22241561b74ef4df3a1aa

ros/README.md

RTSYork/rtscar

134f2e6aaa420fbaa4f22241561b74ef4df3a1aa

# ROS Support Run `build.sh`, or use the following commands in `car-ws` to download and build ROS packages. ``` wstool update rosdep update rosdep install --from-paths src --ignore-src --rosdistro $ROS_DISTRO -y -r catkin_make ``` Then either source the development packages directly: ``` source devel/setup.sh ``` or install the packages and source from their installation directory: ``` catkin_make install source install/setup.sh ```

eng_Latn

f787f7ba0b8b54fc0008ab72f5ef20688b7bf8be

md

Markdown

all/fidl/fuchsia.identity.authentication/README.md

opensource-assist/fuschia-reference-docs

598955f1df1c01e2972f1900d6d08bb591194ab2

all/fidl/fuchsia.identity.authentication/README.md

opensource-assist/fuschia-reference-docs

598955f1df1c01e2972f1900d6d08bb591194ab2

all/fidl/fuchsia.identity.authentication/README.md

opensource-assist/fuschia-reference-docs

598955f1df1c01e2972f1900d6d08bb591194ab2

[TOC] # fuchsia.identity.authentication <p>Defines the protocols used to enroll and interact with user authentication mechanisms.</p> <p>New authentication mechanisms may be added to the system by implementing the server side of one or more of these protocols, the core identity system will act as the client.</p> ## **PROTOCOLS** ## StorageUnlockMechanism {#StorageUnlockMechanism} *Defined in [fuchsia.identity.authentication/mechanisms.fidl](https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/mechanisms.fidl#16)* <p>A stateless interface serving an authentication mechanism capable of supplying pre-key material for use with storage unlock. Clients are responsible for managing and persisting enrollments. Enrollment data created during registration must be provided back during authentication.</p> <p>NOTE: This protocol may not be discoverable in the future.</p> ### Authenticate {#Authenticate} <p>Interactively requests the user to authenticate against any of the provided enrollments.</p> <p><code>enrollments</code> A list of enrollments that will be accepted.</p> <p>Returns: <code>attempt</code> An <code>AttemptedEvent</code> where the <code>enrollment_id</code> refers to one of the provided enrollments, and the optional <code>updated_enrollment_data</code> indicates that the enrollment with said id must also be updated if the attempt is successful.</p> #### Request <table> <tr><th>Name</th><th>Type</th></tr> <tr> <td><code>enrollments</code></td> <td> <code>vector&lt;<a class='link' href='#Enrollment'>Enrollment</a>&gt;[16]</code> </td> </tr></table> #### Response <table> <tr><th>Name</th><th>Type</th></tr> <tr> <td><code>result</code></td> <td> <code><a class='link' href='#StorageUnlockMechanism_Authenticate_Result'>StorageUnlockMechanism_Authenticate_Result</a></code> </td> </tr></table> ### Enroll {#Enroll} <p>Interactively run the enrollment flow for a single enrollment.</p> <p>Returns: <code>enrollment_data</code> Data associated with this enrollment, to be provided during authentication in the future. <code>prekey_material</code> The the pre-key material that will be produced by successfully authenticating against this enrollment.</p> #### Request <table> <tr><th>Name</th><th>Type</th></tr> </table> #### Response <table> <tr><th>Name</th><th>Type</th></tr> <tr> <td><code>result</code></td> <td> <code><a class='link' href='#StorageUnlockMechanism_Enroll_Result'>StorageUnlockMechanism_Enroll_Result</a></code> </td> </tr></table> ## **STRUCTS** ### Enrollment {#Enrollment} *Defined in [fuchsia.identity.authentication/common.fidl](https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#64)* <p>Enrollments allow some authentication mechanisms to produce authentication events. An enrollment must first be created in order to be authenticated against. Both creation and authentication may involve user interaction. An enrollment is typically tied to a user controlled authentication factor, such as a fingerprint, a password or a security key.</p> <table> <tr><th>Name</th><th>Type</th><th>Description</th><th>Default</th></tr><tr> <td><code>id</code></td> <td> <code><a class='link' href='#EnrollmentId'>EnrollmentId</a></code> </td> <td><p>A unique identifier associated with the enrollment.</p> </td> <td>No default</td> </tr><tr> <td><code>data</code></td> <td> <code><a class='link' href='#EnrollmentData'>EnrollmentData</a></code> </td> <td><p>Data associated with the enrollment.</p> </td> <td>No default</td> </tr> </table> ### PositiveEvent {#PositiveEvent} *Defined in [fuchsia.identity.authentication/common.fidl](https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#97)* <p>An authentication event is a statement which an authentication mechanism makes about the presence and/or engagement of an account owner, and thus affecting the entity's authentication state. The effect of an event depends on the properties of the authentication mechanism which created it. A positive authentication event may contribute to an increase in authentication state.</p> <table> <tr><th>Name</th><th>Type</th><th>Description</th><th>Default</th></tr><tr> <td><code>timestamp</code></td> <td> <code><a class='link' href='../zx/'>zx</a>/<a class='link' href='../zx/#time'>time</a></code> </td> <td><p>The time on <code>ZX_CLOCK_UTC</code> when the event completed.</p> </td> <td>No default</td> </tr> </table> ### NegativeEvent {#NegativeEvent} *Defined in [fuchsia.identity.authentication/common.fidl](https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#109)* <p>A negative authentication event may contribute to a decrease in authentication state.</p> <table> <tr><th>Name</th><th>Type</th><th>Description</th><th>Default</th></tr><tr> <td><code>timestamp</code></td> <td> <code><a class='link' href='../zx/'>zx</a>/<a class='link' href='../zx/#time'>time</a></code> </td> <td><p>The time on <code>ZX_CLOCK_UTC</code> when the event completed.</p> </td> <td>No default</td> </tr> </table> ### AttemptedEvent {#AttemptedEvent} *Defined in [fuchsia.identity.authentication/common.fidl](https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#120)* <p>A attempted authentication event may contribute to an increase in authentication state if and only if the pre-key material is correct. Otherwise, it does not affect the authentication state.</p> <table> <tr><th>Name</th><th>Type</th><th>Description</th><th>Default</th></tr><tr> <td><code>timestamp</code></td> <td> <code><a class='link' href='../zx/'>zx</a>/<a class='link' href='../zx/#time'>time</a></code> </td> <td><p>The time on <code>ZX_CLOCK_UTC</code> when the event completed.</p> </td> <td>No default</td> </tr><tr> <td><code>enrollment_id</code></td> <td> <code><a class='link' href='#EnrollmentId'>EnrollmentId</a></code> </td> <td><p>The id of the enrollment used to produce this attempt.</p> </td> <td>No default</td> </tr><tr> <td><code>updated_enrollment_data</code></td> <td> <code><a class='link' href='#EnrollmentData'>EnrollmentData</a></code> </td> <td><p>Enrollment data which should should replace the old enrollment data upon successful authentication. This field is only populated if a change in enrollment data is required.</p> </td> <td>No default</td> </tr><tr> <td><code>prekey_material</code></td> <td> <code><a class='link' href='#PrekeyMaterial'>PrekeyMaterial</a></code> </td> <td><p>Pre-key material produced during the authentication attempt.</p> </td> <td>No default</td> </tr> </table> ### StorageUnlockMechanism_Authenticate_Response {#StorageUnlockMechanism_Authenticate_Response} *generated* <table> <tr><th>Name</th><th>Type</th><th>Description</th><th>Default</th></tr><tr> <td><code>attempt</code></td> <td> <code><a class='link' href='#AttemptedEvent'>AttemptedEvent</a></code> </td> <td></td> <td>No default</td> </tr> </table> ### StorageUnlockMechanism_Enroll_Response {#StorageUnlockMechanism_Enroll_Response} *generated* <table> <tr><th>Name</th><th>Type</th><th>Description</th><th>Default</th></tr><tr> <td><code>enrollment_data</code></td> <td> <code><a class='link' href='#EnrollmentData'>EnrollmentData</a></code> </td> <td></td> <td>No default</td> </tr><tr> <td><code>prekey_material</code></td> <td> <code><a class='link' href='#PrekeyMaterial'>PrekeyMaterial</a></code> </td> <td></td> <td>No default</td> </tr> </table> ## **ENUMS** ### Error {#Error} Type: <code>uint32</code> *Defined in [fuchsia.identity.authentication/common.fidl](https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#16)* <p>Specifies the reason that a fuchsia.identity.authentication method failed.</p> <table> <tr><th>Name</th><th>Value</th><th>Description</th></tr><tr> <td><code>UNKNOWN</code></td> <td><code>1</code></td> <td><p>Some other problem occurred that cannot be classified using one of the more specific statuses. Retry is optional.</p> </td> </tr><tr> <td><code>INTERNAL</code></td> <td><code>2</code></td> <td><p>An internal error occurred. This usually indicates a bug within the component implementing the authentication mechanism. Retry is optional.</p> </td> </tr><tr> <td><code>UNSUPPORTED_OPERATION</code></td> <td><code>3</code></td> <td><p>The requested operation is not supported. This generally indicates that implementation of a new feature is not yet complete. The request should not be retried.</p> </td> </tr><tr> <td><code>INVALID_AUTH_CONTEXT</code></td> <td><code>4</code></td> <td><p>An invalid or non-functional <code>AuthenticationContextProvider</code> was provided. Retrying is unlikely to correct this error.</p> </td> </tr><tr> <td><code>INVALID_REQUEST</code></td> <td><code>5</code></td> <td><p>The request was malformed in some way, such as supplying duplicate enrollment entries. The request should not be retried.</p> </td> </tr><tr> <td><code>INVALID_DATA_FORMAT</code></td> <td><code>6</code></td> <td><p>Data supplied with the request was malformed in some way, such as supplying corrupted enrollment data. The request should not be retried.</p> </td> </tr><tr> <td><code>RESOURCE</code></td> <td><code>7</code></td> <td><p>A local resource error occurred such as I/O, FIDL, or memory allocation failure. Retry, after a delay, is recommended.</p> </td> </tr><tr> <td><code>ABORTED</code></td> <td><code>8</code></td> <td><p>An interactive authentication operation was cancelled by the user.</p> </td> </tr></table> ## **UNIONS** ### StorageUnlockMechanism_Authenticate_Result {#StorageUnlockMechanism_Authenticate_Result} *generated* <table> <tr><th>Name</th><th>Type</th><th>Description</th></tr><tr> <td><code>response</code></td> <td> <code><a class='link' href='#StorageUnlockMechanism_Authenticate_Response'>StorageUnlockMechanism_Authenticate_Response</a></code> </td> <td></td> </tr><tr> <td><code>err</code></td> <td> <code><a class='link' href='#Error'>Error</a></code> </td> <td></td> </tr></table> ### StorageUnlockMechanism_Enroll_Result {#StorageUnlockMechanism_Enroll_Result} *generated* <table> <tr><th>Name</th><th>Type</th><th>Description</th></tr><tr> <td><code>response</code></td> <td> <code><a class='link' href='#StorageUnlockMechanism_Enroll_Response'>StorageUnlockMechanism_Enroll_Response</a></code> </td> <td></td> </tr><tr> <td><code>err</code></td> <td> <code><a class='link' href='#Error'>Error</a></code> </td> <td></td> </tr></table> ## **CONSTANTS** <table> <tr><th>Name</th><th>Value</th><th>Type</th><th>Description</th></tr><tr id="PREKEY_MATERIAL_MAX_SIZE"> <td><a href="https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#10">PREKEY_MATERIAL_MAX_SIZE</a></td> <td> <code>32</code> </td> <td><code>uint32</code></td> <td><p>The maxium size of the prekey material in bytes.</p> </td> </tr> <tr id="ENROLLMENT_DATA_MAX_SIZE"> <td><a href="https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#13">ENROLLMENT_DATA_MAX_SIZE</a></td> <td> <code>256</code> </td> <td><code>uint32</code></td> <td><p>The maxium size of enrollment data in bytes.</p> </td> </tr> <tr id="MAX_ENROLLMENTS"> <td><a href="https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#56">MAX_ENROLLMENTS</a></td> <td> <code>16</code> </td> <td><code>uint32</code></td> <td><p>The maximum number of active enrollments per authentication mechanism and account.</p> </td> </tr> </table> ## **TYPE ALIASES** <table> <tr><th>Name</th><th>Value</th><th>Description</th></tr><tr id="EnrollmentId"> <td><a href="https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#77">EnrollmentId</a></td> <td> <code>uint64</code></td> <td><p>A unique identifier for an <code>Enrollment</code> within an account and an authentication mechanism.</p> </td> </tr><tr id="EnrollmentData"> <td><a href="https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#83">EnrollmentData</a></td> <td> <code>vector</code>[<code><a class='link' href='#ENROLLMENT_DATA_MAX_SIZE'>ENROLLMENT_DATA_MAX_SIZE</a></code>]</td> <td><p>Arbitrary opaque data associated with an authentication enrollment, created and subsequently read by the authentication mechanism that produced the enrollment. It is meaningful only to the authenticator, and opaque to its clients.</p> </td> </tr><tr id="PrekeyMaterial"> <td><a href="https://fuchsia.googlesource.com/fuchsia/+/master/sdk/fidl/fuchsia.identity.authentication/common.fidl#88">PrekeyMaterial</a></td> <td> <code>vector</code>[<code><a class='link' href='#PREKEY_MATERIAL_MAX_SIZE'>PREKEY_MATERIAL_MAX_SIZE</a></code>]</td> <td><p>Pseudo-random data associated with an enrollment of an authentication mechanism capable of storage unlock. It is reproduced only upon successful authentication against that enrollment.</p> </td> </tr></table>

eng_Latn

f788f40221d9101718ec4b9c864d605428b1cea8

md

Markdown

_site/README.md

SPDwebmaster/SPDwebmaster.github.io

e6379ea74a4beaa74a218b5a58326cf4f7b4a9bd

2019-02-09T21:30:46.000Z

2020-06-14T06:08:31.000Z

_site/README.md

SPDwebmaster/SPDwebmaster.github.io

e6379ea74a4beaa74a218b5a58326cf4f7b4a9bd

_site/README.md

SPDwebmaster/SPDwebmaster.github.io

e6379ea74a4beaa74a218b5a58326cf4f7b4a9bd

# SPD Website SPD Beta-Nu website. Based on the Jekyll version of the "Forty" theme by [HTML5 UP](https://html5up.net/). # Credits Original README from HTML5 UP: ``` Forty by HTML5 UP html5up.net | @ajlkn Free for personal and commercial use under the CCA 3.0 license (html5up.net/license) Credits: Demo Images: Unsplash (unsplash.com) Icons: Font Awesome (fontawesome.github.com/Font-Awesome) Other: jQuery (jquery.com) html5shiv.js (@afarkas @jdalton @jon_neal @rem) background-size polyfill (github.com/louisremi) Misc. Sass functions (@HugoGiraudel) Respond.js (j.mp/respondjs) Skel (skel.io) ``` Repository [Jekyll logo](https://github.com/jekyll/brand) icon licensed under a [Creative Commons Attribution 4.0 International License](http://choosealicense.com/licenses/cc-by-4.0/).

kor_Hang

f78900c00c8843879dd501669a68f6442831ae3e

md

Markdown

_posts/0000-01-04-jdxdl.md

jdxdl/github-slideshow

aa4f949e9ba2d2672356a1b9540aa1286390dd35

_posts/0000-01-04-jdxdl.md

jdxdl/github-slideshow

aa4f949e9ba2d2672356a1b9540aa1286390dd35

2019-08-24T12:21:47.000Z

2022-02-26T05:30:55.000Z

_posts/0000-01-04-jdxdl.md

jdxdl/github-slideshow

aa4f949e9ba2d2672356a1b9540aa1286390dd35

--- layout: slide title: "Can't stop adding slides" --- WAAAAAAAAAAAAA!!!

kor_Hang

f7899e9bc984aa859fe2b63fdc4758a84b0e47a2

md

Markdown

_posts/2016-10-25-expected-goals.md

abhinavralhan/abhinavralhan.github.io

8219e1da731ccae11800abbc07c62725ea01fe0a

_posts/2016-10-25-expected-goals.md

abhinavralhan/abhinavralhan.github.io

8219e1da731ccae11800abbc07c62725ea01fe0a

_posts/2016-10-25-expected-goals.md

abhinavralhan/abhinavralhan.github.io

8219e1da731ccae11800abbc07c62725ea01fe0a

--- title: "xG Model" date: 2018-2-21 layout: single author_profile: true comments: true tags: [analytics, data analytics, soccer analytics, xG, expected goals] --- This is a blog post for all soccer analytics enthusiasts, even the beginners. :) ### What ? One of the more enthusiastic experts and analysts, Michael Caley, defined the metric in layman’s terms: “The idea is to quantify the likelihood of a goal being scored from a particular shot attempt (or other scoring chance). This is an idea that I think is quite intuitive. ‘We need to create better scoring chances’ is something managers have said forever, and xG is basically just a quantification of that notion. The broad concept has probably been around for a long time in football — Charles Reep’s notion that ‘one of every nine shots is scored’ is a sort of early version of xG.” Ted Knuston, of Statsbomb, intererstingly said: “It will also bring a new kind of fan to the game, absolutely. This kind of data overlaps with people who play Football Manager or fantasy league. It’s exactly the same thing, you take information about players and you evaluate them. If you want to be better in fantasy league then you need data. In the US almost everyone grows up with fantasy sports as much as the real thing now.” ### How ? The most common factors used in an xG model are distance and angle of the shot. As you can guess, there are differences even within this. For instance, some people measure distance as where the shot was taken from or even how it was delivered to the location before the shot was taken (11tegen11 and Pleuler). Other factors, may be through-balls, free-kicks, corner kicks, whether it was a header or a normal shot, time of the game and so on. This means the factors available for analysis in a model like this could reach anywhere to 50+ factors I suspect. <img src="https://cdn-images-1.medium.com/max/800/0*9xh7Dx3PyJepKJQs.jpg" width="75%"> <img src="https://cdn-images-1.medium.com/max/800/0*zlxSYb8rMenzhE7V.png" width="75%"> ### My xG Model: The idea is to be able to predict what will happen to particular chances and events, whether they will be converted or not, using particular attributes of data. I also use this opportunity to understand the importance of features through machine learning. All of this gives us an idea as to whether an event, if it occurs is likely to be a goal or not. Data: Data provision courtesy of Stratabet. Here, I’ve used English Championship, English Premiership, Bundesliga, France, Spain, Italy, division 1 data. It dates from the beginning of season 16–17 to the current 17–18. Attributes: For now, I’ve used attributes such as ‘icon’ (type of event), ‘shotQuality’ (used values defined by Stratabet), ‘defPressure’, ‘numDefPlayers’, ‘numAttPlayers’, ‘chanceRating’ (used values as defined by Stratabet), ‘type’ (defines passage of play). All attributes are encoded to particular values. The ‘outcome’ variable is binary encoded, ofcourse. Although I’ve used the parameter chanceRating & shotQuality which covers the idea of a shot going in or not, I would also like to incorporate Shot location later on, myself. Now I’ve implemented it in Python and it gets really ugly exporting all of that code to medium so I implemented it in the form of a Jupyter notebook and it’s pretty heavy. I’ve also added some shot location visualizations as a confirmatory bias. <a href="https://github.com/abhinavralhan/xG">Please take a look here for the code.</a> ### This article was written with the aid of StrataData, which is property of Stratagem Technologies. StrataData powers the StrataBet Sports Trading Platform, in addition to StrataBet Premium Recommendations.

eng_Latn

f78a33a4b65feb2e681cb34980445fe5d53abf4b

md

Markdown

README.md

jinlixing/vue-todo-study

4bc70797b0a9eaa2279e064779e96935fe5158ca

README.md

jinlixing/vue-todo-study

4bc70797b0a9eaa2279e064779e96935fe5158ca

README.md

jinlixing/vue-todo-study

4bc70797b0a9eaa2279e064779e96935fe5158ca

# vue-todo-study this is a study project for vue !

eng_Latn

f78c13363e29c81e952a265233d03e28c638e843

md

Markdown

day08.md

i4leader/Python-Learning-Notes

978388e56b3a8e52bed6673c5538450cc475f17e

2020-03-19T12:35:39.000Z

2020-03-19T12:35:39.000Z

day08.md

i4leader/Python-Learning-Notes

978388e56b3a8e52bed6673c5538450cc475f17e

day08.md

i4leader/Python-Learning-Notes

978388e56b3a8e52bed6673c5538450cc475f17e

## day8-面向对象 *** ### 想一想 如何用程序做自我介绍？ * 面向过程:根据业务逻辑从下到上写代码 * 面向对象：对数据与函数绑定到一起，进行封装，这样能够更快速的开发程序，减少了重复代码的重复使用 面向过程编程最易被初学者接受，其往往用一长段代码来实现指定功能，开发过程的思路是将数据和函数按照执行的逻辑顺序组织在一起，数据与函数分开考虑。 ### 类和对象 面向对象编程的2个非常重要的概念：类和对象 对象是面向对象编程的核心，在使用对象的过程中，为了将具有共同特征和行为的一组对象抽象定义，提出另外一个新的概念--类 类就相当于制造飞机时的图纸，用它来进行创建的飞机就相当于对象 #### 1.类 ``` 人以物聚,类以群分. 具有相似内部状态和运动规律的实体的集合(或统称,抽象). 具有相同属性和行为事物的统称 ``` 类是抽象的,在使用的时候通常会找到一个类的一个具体的存在,使用这个具体的存在.一个类可以找到多个对象. #### 2.对象 ``` 某一个具体事物的存在,在现实世界中可以看得见摸得着的. 可以直接使用的 ``` #### 3.类和对象之间的关系 小总结:类就是创建对象的模板 #### 4. #### 5.类的构成 类(class)有3个部分构成 * 类的名称:类名 * 类的属性:一组数据 * 类的方法:允许对进行操作的方法(行为) ##### <1>举例: 1) 人的类设计,只关心3样东西: * 事物名称(类名):人(person) * 属性:身高(height),年龄(age) * 方法(行为/功能):跑(run).打架(fight) 2) 狗类的设计 * 类名:狗(Dog) * 属性:品种,毛色,性别,名字,腿儿的数量 * 方法(行为/功能):叫,跑,咬人,吃,摇尾巴 #### 6.类的抽象 如何把日常生活中的事物抽象成程序中的类? 拥有相同(或者类似)属性和行为的对象都可以抽象出一个类 方法:一般名词都是类(名词提炼法) ### 定义类 定义一个类,格式如下: ``` class 类名: 方法列表 ``` 演示:定义一个Car类 ``` # 定义类 class Car: # 方法 def getCarInfo(self): print('车轮子个数:%d,颜色%s'%(self.wheelNum,self.color)) def move(self): print("车正在移动...") ``` #### 说明: * 定义类时有两种:新式类和经典类,上面的Car为经典类,如果是Car(object)则为新式类 * 类名的命名规则一般是"大驼峰" ### 创建对象 通过上一节课程,定义了一个Car类;就好比有一张车子的图纸,那么接下来就应该把图纸交给工人们生成了 python中,可以根据已经定义的类去创建出一个个对象 创建对象的格式为: ``` 对象名 = 类名() ``` 示例代码: ``` #!/usr/bin/python3 #coding=utf-8 # 定义一个类 class Dog: # 定义一个方法 def bark(self): print("汪汪汪......") def run(self): print("狗疯狂的跑....") # 接下来创建一条狗 xiaogou = Dog() # 调用小狗对象的一个方法 xiaogou.bark() xiaogou.run() # 添加属性 xiaogou.weight = 5 xiaogou.color = '黄色' #获取小狗的属性 print(xiaogou.weight) print(xiaogou.color) ``` 运行结果:  创建对象代码演示: ``` #coding=utf-8 # 定义类 class Car: # 移动 def move(self): print('车在奔跑...') # 鸣笛 def toot(self): print('车在鸣笛...嘟嘟..') # 创建一个对象,并用变量BMW来保存它的引用 BMW = Car() BMW.color = '黑色' BMW.wheelNum = 4 BMW.move() BMW.toot() print(BMW.color) print(BMW.wheelNum) ``` 运行结果:  #### 总结: * BMW = Car(),这样就产生了一个Car的实例对象,此时也可以通过实例对象BMW来访问属性或者方法 * 第一次使用BMW.color = '黑色'表示给BMW这个对象添加属性,如果后面再次出现BMW.color = xxx表示对属性进行修改 * BMW是一个对象,它拥有属性(数据)和方法(函数) ### __init__方法 ### 应用：创建多个对象 ### “魔法”方法 #### 1.打印id() 如果把xiaogou使用print进行输出的话,会看到如下信息:  即看到的是创建出来的xiaogou对象在内存中的地址 #### 2.定义__str__() 方法 ``` def __str__(self): return "hahaha...." ```  限制只需要定义好\_\_str\_\_()就可以指定输出内容 ##### 总结 * 在python中方法名如果是__xxx__()的,那么就有特殊功能,因此叫做"魔法"方法 * 当使用print输出对象的时候,只要自己定义了 \_\_str\_\_(self)方法,那么就会打印从这个方法中return的数据 ### self #### 1.理解self 看如下示例: ``` # 定义一个类 class Animal: # 方法 def __init__(self,name): self.name = name def printName(self): print('名字为:%s'%self.name) # 定义一个函数 def myPrint(animal): animal.printName() dog1 = Animal('西西') myPrint(dog1) ``` 运行结果:  #### 总结 * 所谓self,可以理解为自己 * 可以把self当做C++中类里面的this指针一样理解,就是对象自身的意思 * 某个对象调用其方法时,python解释器会把这个对象作为第一个参数传递给self,所以开发者只要传递后面的参数即可 ### 应用:烤地瓜 为了更好的理解面向对象编程,下面以"烤地瓜"为案例,进行分析 #### 1.分析"烤地瓜"的属性和方法 ##### 示例属性如下: * cookedLevel: 这是数字;0~3表示半生不熟,超过5表示已经烤好了,超过8表示已经烤成木炭了!我们的地瓜开始时是生的 * cookedString:这是字符串;描述地瓜的生熟程度 * condiments:这是地瓜的配料列表,比如番茄酱,芥末酱等 ##### 示例方法如下: * cook():把地瓜烤一段时间 * addCondiments():给地瓜添点配料 * \_\_init\_\_():设置默认的属性 * \_\_str\_\_():让print的结果看起来更好一些 #### 2.定义类,并且定义 \_\_init\_\_() 方法 ``` # 定义"地瓜"类 class SweetPotato: '这是烤地瓜的类' # 定义初始化方法 def __init__(self): self.cookedLevel = 0 sefl.cookedString = "生的" self.condiments =[] ``` #### 3.添加"烤地瓜"方法 ``` #烤地瓜的方法 # 用火去考地瓜 def cook(self,time): self.cookedLevel += time if self.cookedLevel > 8: self.cookedString = "烤糊了" elif self.cookedLevel > 5: self.cookedString = "熟了" elif self.cookedLevel > 3: self.cookedString = "半生不熟" else: self.cookedString = '生的' ``` #### 4. 完整代码 ``` # 定义"地瓜"类 class SweetPotato: '这是烤地瓜的类' # 定义初始化方法 def __init__(self): self.cookedLevel = 0 self.cookedString = "生的" self.condiments =[] #定制Print打印这个对象的时候,显示的内容 def __str__(self): msg = "您的地瓜已经处于" + self.cookedString + "状态 " if len(self.condiments)>0: msg += ",添加的佐料为:" for temp in self.condiments: msg += temp + ", " msg = msg.strip(", ") return msg # 用火去考地瓜 def cook(self,time): self.cookedLevel += time if self.cookedLevel > 8: self.cookedString = "烤糊了" elif self.cookedLevel > 5: self.cookedString = "熟了" elif self.cookedLevel > 3: self.cookedString = "半生不熟" else: self.cookedString = '生的' # def addCondiments(self,temp): self.condiments.append(temp) # 创建一个地瓜对象 digua = SweetPotato() print('-'*6+'接下来开始烤'+'-'*6) print('---------烤两分钟--------') digua.cook(2) print(digua) print('---------又烤两分钟--------') digua.cook(2) print(digua) print('-'*6+'添加番茄酱'+'-'*6) digua.addCondiments("番茄酱") print(digua) print('-'*6+'添加芥末酱'+'-'*6) digua.addCondiments("芥末酱") print(digua) print('---------又烤两分钟--------') digua.cook(2) print(digua) ``` 输出结果:  ### 隐藏数据 可能你已经意识到,查看或者修改对象的属性(数据),有2种方法 #### 1.直接通过对象名修改 ``` SweetPotato.cookedLevel = 5 ``` #### 2.通过方法间接修改 ``` SweetPotato.cook(5) ``` #### 分析 明明可以通过直接修改的方法,为啥还要定义方法来间接修改呢? 至少有两个原因: * 如果直接修改属性,烤地瓜至少需要修改2部分,即修改cookedLevel和cookedString.而使用方法来修改时,只需要调用一次即可完成 * 如果直接访问属性,可能会出现一些数据设置错误的情况产生例如 cookedLevel = -3.这会使地瓜比以前还生,当然这也没有任何意义,通过使用方法来进行修改,就可以在方法中进行数据合法性的检查 ### 应用:存放家具 ``` #!/bin/bash/python3 #coding=utf-8 # 定义yige home 家类 class Home: def __init__(self,area): self.area = area self.rongNaList = [] def __str__(self): msg = "家当前可用的面积为:" + str(self.area) return msg def containItem(self, item): bedArea = int(item.getBedArea()) if self.area > bedArea: self.rongNaList.append(item) self.area -= bedArea # 定义一个bed类 class Bed: def __init__(self,name,area): self.area = area self.name = name def __str__(self): msg = "床占用的面积为:" + str(self.area) return msg def getBedArea(self): return self.area home = Home(180) print(home) bed = Bed("席梦思床","4") print(bed) home.containItem(bed) print(home) ``` 运行结果:  *** 有兴趣一起学习的可以加我微信，大家一起交流。加我请备注“13天Python学习” 

yue_Hant

f78d5744aeef432ff15c0bc13485820b300a6edd

md

Markdown

README.md

haibinzhang/unity_learning

c3996235af92661a617c7df22acc18c0c67969ac

README.md

haibinzhang/unity_learning

c3996235af92661a617c7df22acc18c0c67969ac

README.md

haibinzhang/unity_learning

c3996235af92661a617c7df22acc18c0c67969ac

# unity_learning Hub for Unity Knowledge

eng_Latn

f78d5bad059ced11a643a1b36b9a7542f1a48573

md

Markdown

README.md

yoo2001818/webglue-collada-loader

88ccdb2fc129f11c6d6d10fcf100b7fcec2d1182

README.md

yoo2001818/webglue-collada-loader

88ccdb2fc129f11c6d6d10fcf100b7fcec2d1182

README.md

yoo2001818/webglue-collada-loader

88ccdb2fc129f11c6d6d10fcf100b7fcec2d1182

# webglue-collada-loader COLLADA 1.4 (.dae) loader for webglue

kor_Hang

f78db94e3e3851f71852cc55bb89d4b460e7b8ae

md

Markdown

_includes/05-emphasis.md

prafful-T4545/markdown-portfolio

8721669f46161945cedb76e874b1d3a5cb532459

_includes/05-emphasis.md

prafful-T4545/markdown-portfolio

8721669f46161945cedb76e874b1d3a5cb532459

2021-07-12T05:26:18.000Z

2021-07-12T05:51:21.000Z

_includes/05-emphasis.md

prafful-T4545/markdown-portfolio

8721669f46161945cedb76e874b1d3a5cb532459

*This text will be Italic* __This text will be bold__

eng_Latn

f78e943201de7b4710c07f06c2a4986276b14e5e

md

Markdown

README.md

wjlewis/ramo

ed06a54c553bd2801c530dde3806192d55a68e3b

2019-07-07T22:23:00.000Z

2022-01-22T16:41:49.000Z

README.md

wjlewis/ramo

ed06a54c553bd2801c530dde3806192d55a68e3b

2020-07-22T01:13:29.000Z

2021-09-25T14:33:05.000Z

README.md

wjlewis/ramo

ed06a54c553bd2801c530dde3806192d55a68e3b

# ramo ```javascript run()(q => exist(terms => [ appendo(['miniKanren'], ['for', 'JavaScript'], terms), membero(q, terms) ])).join(' ') // => 'miniKanren for JavaScript' ``` ## Install ``` $ npm i ramo ``` ## Overview `ramo` is a port of Friedman, Byrd, et al.'s `miniKanren` to JavaScript. The canonical implementations of `miniKanren` are written in Scheme, and while Scheme and JavaScript share many features in common, they have plenty of differences as well. I have tried to preserve the semantics, and&mdash;more importantly&mdash;the charm of `miniKanren` in a package that I hope will be enjoyed by (and perhaps useful to) JavaScript programmers. ## Tutorial I'd like to spend the next few paragraphs demonstrating the most important features that `ramo` offers by analyzing a number of examples, culminating in [a solution to the famous *Zebra Puzzle*](#the-zebra-puzzle). ### Relations and Goals `ramo` is a relational extension for JavaScript. 'Relational' because it deals with *relations* in contrast to functions. Relations are similar to functions, but the notion of a relation makes no distinction between inputs and outputs. In that way, relations are a generalization of functions. A relation allows one to express the idea that some relationship holds between its arguments, *or could be made to hold between its arguments*. When a relation is applied to arguments, it is known as a *goal*. A goal represents a search to find a way to satisfy the relationship in question. In general there may be no way to do this, there might be a single way, many ways, or an infinite number of ways. Thus, executing a goal does not produce a single value, but a *set* of values, each of which represents a way to satify its underlying relation. The most important `ramo` relation is `eq`, which allows one to express that two arguments are equivalent (in a special way). When `eq` is applied to two arguments, it becomes a *goal* which can be *run* to produce solutions: ```javascript const { run, eq } = require('ramo'); const g1 = eq(3, 3); // This is a goal that succeeds if 3 === 3 const results1 = run()(q => g1); // => ['_0'] (a single success) const g2 = eq(3, 'three'); // This is a goal that succeeds if 3 === 'three' const results2 = run()(q => g2); // => [] (no successes) ``` What is `q` in those previous examples? And what does `'_0'` mean? The answers to both of these questions are entwined with the special nature of `eq` as alluded to above. In the examples above, `q` is a *logic variable*. A logic variable is a special kind of variable that can become associated ("bound") with another value through a process known as *unification*. The relation `eq` is special because it *unifies* its arguments: ```javascript const results1 = run()(q => eq(q, 3)); // => [3] const results2 = run()(q => eq(q, 'three')); // => ['three'] const results3 = run()(q => eq(q, { complex: 'val' })); // => [{ complex: 'val' }] ``` In the first example above, the goal `eq(q, 3)` can be satisfied if the logic variable `q` is bound to the value `3`. Thus, when it is run, this goal produces a result set with a single value: `3`. As the other examples show, a logic variable can be unified with a wide variety of JavaScript values. What about the following example? ```javascript const results = run()(q => eq(q, { contains: q })); // => [] ``` Since the value `{ contains: q }` *contains* the logic variable `q`, there is no way that these two values can be made equivalent (in any non-pathological sense of the term). This provision is known as the "occurs check", and with it in mind, we can now formulate the rules for unification (and thus `eq`): 1. Two equal (`===`) primitive JavaScript values unify 2. An unbound ("fresh") logic variable unifies with any JavaScript value (including another logic variable) in which it does not occur; furthermore, this variable becomes bound to the value in question 3. Two JavaScript objects unify if they have the same keys, and each of the values associated with the same keys unify; as in (2), variables may be bound during this process 4. All bound logic variables are first replaced by their associated values before the unification process To further illustrate these principles, consider the following: ```javascript const results = run()(q => eq({ includes: q }, { includes: { another: 'object' } })); // => [{ another: 'object' }] ``` `eq` unifies `{ includes: q }` and `{ includes: { another: 'object' } }` by noting that if `q` is bound to `{ another: 'object' }`, the two values become equal. Thus, unification may be seen as a process of "filling in holes" in an attempt to make two expressions equal; the "holes" in this case are logic variables. We now have a single relation, `eq`, that allows us to produce goals, and we know how to introduce a single logic variable and execute a single goal using `run`. We will now see some other relations, other ways to introduce logic variables, and ways to run multiple goals. ### Combining Goals Given several goals, there are two main ways we might wish to combine them into a compound goal. We might wish for our compound goal to succeed if *all* of the goals are satisfied (conjunction), or if *any* of the goals are satisfied (disjunction). To form a conjunction of goals (*all*) in `ramo`, simple place the goals in an Array, like so: ```javascript const results1 = run()(q => [ eq(q, 'first'), // q must unify with 'first' eq(42, 42) // AND 42 must unify with 42 ]); // => ['first'] const results2 = run()(q => [ eq(q, 'first'), // q must unify with 'first' eq(q, 'second') // AND q must unify with 'second' ]); // => [] ``` In the second example, the first goal succeeds, binding `q` to `'first'`, and then the second goal is executed. In order for it to succeed, `q` must be unified with `'second'`. However, since `q` is already bound to `'first'`, this is impossible. To form a disjunction of goals (*any*), we introduce a new function `conde`; simply call `conde` with the goals as arguments: ```javascript const { run, eq, conde } = require('ramo'); const results1 = run()(q => conde( eq(q, 'first'), // q must unify with 'first' eq(q, 'second') // OR q must unify with 'second' )); // => ['first', 'second'] ``` In thise case, the compound goal succeeded in *two* ways, corresponding to the ways in which each constituent goal succeeds. Lastly, we should note that conjuctions (`[...]`) and disjunctions (`conde(...)`) can be freely combined to form even more complex goals, as in: ```javascript const results = run()(q => [ conde( eq(q, 41), eq(q, 42), eq(q, 43) ), eq({ p: q }, { p: 42 }) ]); // => [42] ``` The first goal in the conjunction succeeds with the result set `[41, 42, 43]`, but only one of these solutions satisfies the second goal. Thus, the lone solution is `42`. ### Introducing Fresh Variables At the moment, we are aware of only a single way to introduce a logic variable: using `run`. We can introduce any number of unbound ("fresh") logic variables using the function `exist`. Here is an example: ```javascript const { run, eq, exist } = require('ramo'); run()(q => exist((x, y) => [ eq(x, 'one'), eq(y, false), eq(q, [x, y]) ])); // => [['one', false]] ``` The `exist` form is essential for constructing complex terms from simple ones. The example above, though contrived, illustrates this point: `exist` introduces two fresh variables which are separately bound to `'one'` and `false`, respectively; finally, `q` is bound to the compound value `['one', false]`. ### More Relations Aside from `eq`, `ramo` provides 2 additional primitive relations, along with 4 relations for working with lists below). The primitive relations are `succeedo` and `failo`. The first produces a goal that always succeeds, and the second a goal that always fails: ```javascript const { run, succeedo, failo } = require('ramo'); const results1 = run()(q => [ eq(q, 'satisfied'), succeedo ]); // => ['satisfied'] const results2 = run()(q => [ eq(q, 'unsatisfied'), failo ]); // => [] ``` The relations related to lists are `conso`, `firsto`, `resto`, and `nilo`. The require a bit of an introduction. `conso(a, d, l)` is a goal that succeeds if `l` is a list whose first element is `a` and the rest of whose elements are the list `d` (although this isn't the whole story; see [Lists](#lists)): ```javascript const { run, conso } = require('ramo'); const results1 = run()(q => conso(q, [2,3], [1,2,3])); // => [1] const results2 = run()(q => conso(1, q, [1,2,3])); // => [[2,3]] const results3 = run()(q => conso(1, [2,3], q)); // => [[1,2,3]] ``` Hopefully the true versatility of relations is becoming clearer at this point. The relations `firsto`, `resto`, and `nilo` are used similarly: `firsto(l, a)` succeeds if `a` is the first element of `l`, `resto(l, d)` succeeds if `d` is the rest of the elements of `l`, and `nilo(l)` succeeds if `l` is the empty list (`[]`): ```javascript const { run, firsto, resto, nilo } = require('ramo'); const results1 = run()(q => firsto(['a', 'b', 'c'], q)); // => ['a'] const results2 = run()(q => resto(['a', 'b', 'c'], q)); // => [['b', 'c']] const results3 = run()(q => nilo(q)); // => [[]] ``` ### Defining Relations Just as functions can be used to extend the "vocabulary" of JavaScript with new computations, so too can the vocabulary of `ramo` be extended with user-defined relations. The `Rel` function constructs relations, and it is used like so: ```javascript const { run, Rel, eq, conde } = require('ramo'); const eitherOro = Rel(q => conde( eq(q, 'either'), eq(q, 'or') )); const results = run()(q => eitherOro(q)); // => ['either', 'or'] ``` However, the real power of user-defined relations lies in the fact that they can be recursive: ```javascript const { run, Rel, eq, conde, exist, firsto, resto } = require('ramo'); // membero(x, xs) <= x is a member of the list xs. const membero = Rel((x, xs) => conde( firsto(xs, x), exist(rest => [ resto(xs, rest), membero(x, rest) ]) )); const results1 = run()(q => membero(1, [1,2,3])); // => ['_0'] const results2 = run()(q => membero(q, [1,2,3])); // => [1,2,3] ``` As a final example of a user-defined relation, we will show a definition of `appendo` (a relational programming classic). `appendo(xs, ys, zs)` is a goal that succeeds when the list `zs` is equal to the concatenation of the lists `xs` and `ys`: ```javascript const { run, Rel, conde, exist, eq, conso, nilo } = require('ramo'); const appendo = Rel((xs, ys, zs) => conde( [nilo(xs), eq(ys, zs)], exist((a, d, res) => [ conso(a, d, xs), conso(a, res, zs), appendo(d, ys, res) ]) )); // It can be used to append two lists: const results1 = run()(zs => appendo([1,2,3], [4,5], zs)); // => [[1,2,3,4,5]] // Or to generate one given the other two: const results2 = run()(xs => appendo(xs, [4,5], [1,2,3,4,5])); // => [[1,2,3]] // Or to generate all possible pairs that append to a third: const results3 = run()(q => exist((xs, ys) => [ eq(q, [xs, ys]), appendo(xs, ys, [1,2,3]) ])); // => [[[], [1,2,3]], // [[1], [2,3]], // [[1,2], [3]], // [[1,2,3], []]] ``` ### <a href="the-zebra-puzzle"></a>The Zebra Puzzle Here is a classic AI puzzle (snarfed from Norvig's *PAIP*): 1. There are five houses in a line, each with an owner, a pet, a cigarette, a drink, and a color. 2. The Englishman lives in the red house. 3. The Spaniard owns the dog. 4. Coffee is drunk in the green house. 5. The Ukrainian drinks tea. 6. The green house is immediately to the right of the ivory house. 7. The Winston smoker owns snails. 8. Kools are smoked in the yellow house. 9. Milk is drunk in the middle house. 10. The Norwegian lives in the first house on the left. 11. The man who smokes Chesterfields lives next to the man with the fox. 12. Kools are smoked in the house next to the house with the horse. 13. The Lucky Strike smoker drinks orange juice. 14. The Japanese smokes Parliaments. 15. The Norwegian lives next to the blue house. The questions are: who drinks water and who owns the zebra? We can express these conditions as a series of relations, and then run the appropriate goal to solve the puzzle. Most statements have the form: "such-and-such goes with such-and-such", indicating some partial information about a house. If we represent each house as a list with the scheme: `[owner, pet, cigarette, drink, color]`, then (2) asserts that `membero(['Englishman', ep, ec, ed, 'red'], houses)`, where `houses` is a logic variable representing the list of houses, and `ep`, `ec`, and `ed` represent the Englishman's pet, cigarette choice, and drink, respectively. This solution will work, but it will require a large number of fresh variables (a la `exist((ep, ec, ed, sc, sp, ...) => ...)`). Furthermore, we aren't going to actually use these variable to construct our solution. Fortunately, `ramo` allows us to introduce a "wildcard" or "don't care" variable, typically written as `_` (see [Wildcard](#wildcard)). Each occurrence of this variable is *distinct*; in this way it is reminiscent of Prolog's `_`. Thus, we can restate the goal above as `membero(['Englishman', _, _, _, 'red'], houses)`. Aside from `membero` it is clear that we need relations to express the relationships "next to" (11, 12, 15), and "immediately to the right of" (6). We define these, along with `membero` now: ```javascript const { run, Rel, conde, exist, eq, firsto, resto, conso } = require('ramo'); // membero(x, xs) <= x is a member of the list xs. const membero = Rel((x, xs) => conde( firsto(xs, x), exist(d => [ resto(xs, d), membero(x, d) ]) )); // righto(r, l, xs) <= r is directly to the right of l in xs. const righto = Rel((r, l, xs) => exist(d => [ resto(xs, d), conde( [firsto(xs, l), firsto(d, r)], righto(r, l, d) ) ])); // nexto(x, y, xs) <= x is next to y in xs. const nexto = Rel((x, y, xs) => conde( righto(x, y, xs), righto(y, x, xs) )); ``` We are now ready to express the statements as goals: ```javascript // house scheme: [owner, pet, cigarette, drink, color] const puzzleo = Rel((waterDrinker, zebraOwner, _) => exist(houses => [ eq(houses, [_, _, _, _, _]), // 1 membero(['Englishman', _, _, _, 'red'], houses), // 2 membero(['Spaniard', 'dog', _, _, _], houses), // 3 membero([_, _, _, 'coffee', 'green'], houses), // 4 membero(['Ukrainian', _, _, 'tea', _], houses), // 5 righto([_, _, _, _, 'green'], [_, _, _, _, 'ivory'], houses), // 6 membero([_, 'snails', 'Winston', _, _], houses), // 7 membero([_, _, 'Kools', _, 'yellow'], houses), // 8 eq(houses, [_, _, [_, _, _, 'milk', _], _, _]), // 9 eq(houses, [['Norwegian', _, _, _, _], _, _, _, _]), // 10 nexto([_, _, 'Chesterfields', _, _], [_, 'fox', _, _, _], houses), // 11 nexto([_, _, 'Kools', _, _], [_, 'horse', _, _, _], houses), // 12 membero([_, _, 'Lucky Strike', 'Orange Juice', _], houses), // 13 membero(['Japanese', _, 'Parliaments', _, _], houses), // 14 nexto(['Norwegian', _, _, _, _], [_, _, _, _, 'blue'], houses), // 15 membero([waterDrinker, _, _, 'water', _], houses), // Q1 membero([zebraOwner, 'zebra', _, _, _], houses) // Q2 ])); ``` Lastly, we simply have to run this goal in the appropriate context. We are only interested in a single solution to the goal (if it has one), and we can indicate this by calling `run` with an argument of `1`, as in `run(1)`. In general, `run()(goal)` produces a solution set containing *all* solutions to `goal`, and `run(n)(goal)` produces no more than the first `n`. ```javascript const answer = run(1)((q, _) => exist((waterDrinker, zebraOwner) => [ eq(q, { waterDrinker, zebraOwner }), puzzleo(waterDrinker, zebraOwner, _) ])); // => [{ waterDrinker: 'Norwegian', zebraOwner: 'Japanese' }] ``` To introduce the "wildcard" variable, we simply passed an anonymous function with 2 parameters to `run(1)` instead of 1; the second parameter represents the wildcard. ### Where to learn more The best way to learn `miniKanren` is to work through Friedman, Byrd, et al.'s book "The Reasoned Schemer". However, if you are unpracticed with the Scheme programming language, it will be worth your while to learn it first. Scheme is a profoundly beautiful formalism and is worth comtemplating for its own sake. To learn Scheme, I can highly recommend two resources: Abelson and Sussman's timeless classic "Structure and Interpretation of Computer Programs", and Friedman and Felleisen's "The Little Schemer". Aside from "The Reasoned Schemer", Will Byrd's dissertation is full of insights into `miniKanren`, along with discussions and implementations of various additions. Lastly, if you are interested in the logic programming paradigm in general, two additional resources come to mind. The first is Sterling and Shapiro's "The Art of Prolog", and the second is Norvig's "Paradigms of Artificial Intelligence Programming". ## Additional Features There is one feature of `ramo` that is not available in canonical `miniKanren`, and one quirk that is not present there as well. ### <a href="wildcard"></a>Wildcard The feature is the quite useful "wildcard" variable, analagous to the underscore `_` in Prolog. This variable represents a logic variable that you may wish to take part in a computation, but whose value does not concern you. Each occurrence of the wildcard variable represents a *distinct* logic variable, and thus ```javascript run()((q, _) => eq(q, [_, _, _, _])) // => ['_0', '_1', '_2', '_3'] ``` ### <a href="lists"></a>Lists If lists are the heart of Scheme, then object literals are the heart of JavaScript. And so, as the canonical `miniKanren` implementations lean heavily on the list (well, the *cons-cell*), `ramo` is built atop the object. There is one unfortunate consequence of this arrangement: it would be convenient to use JavaScript Arrays to represent lists, but there is no easy way to treat them in the usual inductive sense. Objects are convenient because we can, in a sense, destructure them via unification; however, Arrays do not share this property. For this reason, `ramo` "desugars" JavaScript Arrays into a *cons-cell* representation that is used internally. During the reification process, these cons-cells are transformed back into Arrays if this is possible. These cons-cells use private `Symbol`s as their keys, so there is no worry about having a non-Array value inadvertently treated as a list. To allow you to generate these cons-cells yourself, `ramo` exports three functions: `cons`, `first`, and `rest`. The function `cons` constructs a cons-cell, `first` extracts a cons-cell's *car*, and `rest` extracts the *cdr*. Lastly, the empty Array (`[]`) represents the empty list. ## Looking Forward At this stage, `ramo` still lacks several features of `miniKanren`, namely `conda`, `condu`, and `project`. I believe these will be straightforward to add in. I also hope to incorporate some features from constraint logic programming and nominal logic programming, as described in Byrd's thesis, although I anticipate these will take more time. At the moment, this package is also weighed down by several inefficiencies, the tradeoffs of which are increased clarity in the source code. Once I am confident in the state of affairs, I will look into improving this situation.

eng_Latn

f78ef5849443dbf7b126576887be268bd8ad589d

md

Markdown

Usage.md

artiso-solutions/roboTXT

273fb23ddc9fee751f94b44e212c030be0fb3d53

2016-09-15T14:14:11.000Z

2021-04-20T07:11:41.000Z

Usage.md

artiso-solutions/roboTXT

273fb23ddc9fee751f94b44e212c030be0fb3d53

2016-09-30T05:34:24.000Z

2017-01-16T13:55:53.000Z

Usage.md

artiso-solutions/robotics-txt-net

273fb23ddc9fee751f94b44e212c030be0fb3d53

# Controlling Motors There are two high level components available for controlling the digital outputs for the motors connected to the fischertechnik TXT controller * [ControllerSequencer](#using-the-controllersequencer) * [MotorPositionController](#using-the-motorpositioncontroller) as well as a few pre-defined values like numbered motors and inputs. # Getting input values There is one high level component for accessing input values present on the fischertechnik TXT controller * [ControllerSequencer](#using-the-controllersequencer) as well as several options to connect inputs with movement operations. ## Using the ControllerSequencer Each hardware controller is accessed via an individual "ControllerSequencer". In order to establish a connection to the hardware first instantiate the "ControllerSequencer". The constructor accepts an ip address or a resolvable hostname. Disposing the instance will close the connection. After instantiating, the sequencer provides basic high level operations like * void StartMotor(Motor, Speed, Direction) * void StopMotor(Motor) * bool GetDigitalInputState(DigitalInput) as well as complex operations like * async Task\<bool> StartMotorStopWithDigitalInputAsync(Motor, Speed, Direction, DigitalInput, ExpectedInputState, Timeout) * async Task StartMotorStopAfterTimeSpanAsync(Motor, Speed, Direction, Timespan) * IObservable\<bool> GetDigitalInputStateChanges(DigitalInput) Also provided is an operation to configure motors with distance counters to be [trackable](#using-the-motorpositioncontroller). Using these motors it is possible to [save and load positions](#saving-and-loading-positions) ## Using the MotorPositionController This component is only for motors with an associated distance counter. It cannot be directly instantiated using the constructor. Instead use "ConfigureMotorPositionController" on an active "ControllerSequencer" to configure a motor to use position tracking. In order to configure a motor a "MotorConfiguration" must be provided. Calling state-changing operations on a configured motor using the "ControllerSequencer" will result in an "InvalidOperationException". After successfully configurating a motor the "MotorPositionController" will provide high level movement operations respecting the configured distance limits. It is also possible to move to specific positions. These positions can be [saved and loaded](#saving-and-loading-positions). ## Saving and loading positions Using the "ControllerSequencer" and configuring motors with distance tracking it is possible to save and load positions. Only the position of tracked motors will be saved (can be disabled for specific motors). To load and save positions call the corresponding operations on the "ControllerSequencer". Positions are saved to a JSON formatted file giving each position a name. The position file is named based on the configured ApplicationName for the sequencer.

eng_Latn

f78f9fc965b446e9e5fdf4d6f559acbe865d7af1

md

Markdown

README.md

ShogoTakeuchi/nextjs-redux-template

ed027519a8eca7495e878589ec2410643707e89e

README.md

ShogoTakeuchi/nextjs-redux-template

ed027519a8eca7495e878589ec2410643707e89e

README.md

ShogoTakeuchi/nextjs-redux-template

ed027519a8eca7495e878589ec2410643707e89e

# Next.js Redux Template Next.js and React/Redux code template with Firebase Authentication ## Configuration src/configs/firebase.ts ``` const config = { apiKey: "", authDomain: "", databaseURL: "", projectId: "", storageBucket: "", messagingSenderId: "", appId: "" }; ``` ## Run ``` $ yarn $ yarn run dev ```

eng_Latn

f78fb3e05bad3cdc8b6c6b1ab0f4a164f1fb850c

md

Markdown

_pages/about.md

0xaead/blog

88ff23a4daf7d0e19f74857d4187b52b4a623d19

_pages/about.md

0xaead/blog

88ff23a4daf7d0e19f74857d4187b52b4a623d19

_pages/about.md

0xaead/blog

88ff23a4daf7d0e19f74857d4187b52b4a623d19

minimalist's [post]

eng_Latn

f78fe0a26d47398e60c8e3ea5cf2675eab321936

md

Markdown

README.md

Sudhamsh/TerraformScripts

88db64aac8a69c46ec89c8aec8f80c5e8882eb67

README.md

Sudhamsh/TerraformScripts

88db64aac8a69c46ec89c8aec8f80c5e8882eb67

README.md

Sudhamsh/TerraformScripts

88db64aac8a69c46ec89c8aec8f80c5e8882eb67

# TerraformScripts Goal is to capture terraformscripts sample scripts for learning. Terraform is an awesome way to implement IaaC. I have seen considerable number of problems in my 7+ years expeience in SRE Infrastructure space. Most of these problems were a results of manual efforts, no repeatable steps, tribal knowledge in some one's head, etc. Most of these problems can be solved if you consider your infrastructes as code. Terraform allows Cloud regions and Availability Zones to be built with code, which is a great value to represent your data centers. ## Getting Started Follow Terraform install scripts using https://www.terraform.io/intro/index.html ### Prerequisites Terraform CLI is installed AWS account ### Installing AWS credentials are set in ~/.aws/credentials file. Create an account if you don't one using https://aws.amazon.com/. You can destory your terrform created objects in a single command to avoid on-going costs. ## Running the tests Explain how to run the automated tests for this system ### And coding style tests Follow terraform coding format ## Deployment Add additional notes about how to deploy this on a live system ## Authors * **Sudhamsh Bachu** - *Initial work* - (https://github.com/Sudhamsh) ## License This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details ## Acknowledgments * Terraform getting started * Terraform: Up and Running: Writing Infrastructure as Code - By Yevgeniy Brikman

eng_Latn

f790dc789f29313e78972b09ac7f8f159c96ad40

md

Markdown

slides/popular-document-datastores.md

ukmadlz/nosql-is-a-lie-devtalks-2016

d8311eb3da6c030df4b9cda5b1210a8152a12a2a

slides/popular-document-datastores.md

ukmadlz/nosql-is-a-lie-devtalks-2016

d8311eb3da6c030df4b9cda5b1210a8152a12a2a

2020-04-24T14:10:03.000Z

2020-04-24T14:10:03.000Z

slides/popular-document-datastores.md

ukmadlz/nosql-is-a-lie-vdb16

3ede061a7b6353bb2d87fb45376fb4c882bb3316

# Popular Document Datastores Cloudant, CouchDB, MongoDB, Couchbase, RethinkDB, RavenDB, GemFire, PouchDB, Microsoft Azure DocumentDB, Datameer, CloudKit, Mnesia, Google Cloud Datastore, TokuMX, Clusterpoint, Terrastore, RaptorDB, EJDB, SisoDb, WhiteDB, Sequoiadb, JasDB, LokiJS, DensoDB, Djondb, FaunaDB, FleetDB, SenseiDB

krc_Cyrl

f793a21903b9a948f9cc60f3393b4fa68e418655

md

Markdown

Readme.md

schets/c_flat_combining

4d8438ac8ab11af86818fdcbf577de43d1d6df8d

2017-02-27T18:33:38.000Z

2017-11-14T01:02:36.000Z

Readme.md

schets/c_flat_combining

4d8438ac8ab11af86818fdcbf577de43d1d6df8d

Readme.md

schets/c_flat_combining

4d8438ac8ab11af86818fdcbf577de43d1d6df8d

A basic flat-combining library for C

eng_Latn

f7948002f9bcbf28c3a5d632be678d0ad0add013

md

Markdown

思考/2015-09-05-periodically-anxiety.md

JimmyLv/jimmylv.github.io

23a86b6d2b8b64eedf0253377922b5862cbf725f

2016-09-30T05:16:42.000Z

2022-03-11T06:45:23.000Z

思考/2015-09-05-periodically-anxiety.md

TheLittleStars/jimmylv.github.io

23a86b6d2b8b64eedf0253377922b5862cbf725f

2016-09-15T02:15:58.000Z

2022-03-21T10:01:52.000Z

思考/2015-09-05-periodically-anxiety.md

TheLittleStars/jimmylv.github.io

23a86b6d2b8b64eedf0253377922b5862cbf725f

2016-09-15T10:04:55.000Z

2022-01-26T09:08:01.000Z

--- layout: post title: 周期性大姨夫：一篇关于梦想和生活的咆哮 categories: [思考] tags: [生活] published: True --- # 周期性大姨夫 突然又开始莫名地焦虑了，来想想原因和 Action 吧，传说中的大姨夫又来咯。有点儿为了写东西而写东西了，但是我却想不到什么其他的方式来消除焦虑。 回顾一下今天的一天，早上八点就起床了，以为自己能利用好时间，可是可是呢？艹！大概就是因为什么也没做吧，一方面觉得自己浪费了时间，一方面觉得大部分时间又花在了维护生活成本上，艹！生活上已经没有了认真，到底该怎么调整到一个好的状态？节约时间还是继续保持热爱去享受生活？我不知道，我把节约了的时间去做了什么？啥成果也没有哇，那我到底有什么动力去争取更多的时间？ 我不服我现在的状态，不服现在的自己，把自己归于何处？置于何地？ WTF!热情真的会减，不管做什么事情，而我这个人，最缺乏的就是坚持的精神，现在来说我到底有坚持什么事情呢？ ## 生活维护成本 在知乎上有一个问题：[我们是如何一步一步走向平庸的？](http://www.zhihu.com/question/33220674/answer/57897678)，有个答案的理论是**我们大部分时间花在维护成本上**，对于大多数人来说，维持现今的人生就已十分吃力。每天做个饭，保持基本的身体健康就已经花去了大部分的时间，不知不觉时间就没有了。 可是让人忧伤的是，如果一定要这样功利得去计算生活的维系成本，那就像人性是禁不起考验的，一旦开始了计较，生活也就没有了任何趣味。以往可能还会自己做做饭，享受一下做饭的过程，虽然时间难免长了点，可是吃到嘴里的好味道便也就让这个过程幸福了一些。可是万一，就像今天中午一样，做得如此难吃呢？是不是就该放弃，转向快而方便的其他下馆子的方式。很多人并不是最开始就是为了享受生活而做饭，而是因为迫于生计不得已用时间来换省钱，如何够便宜够方便的话我一定去吃又营养又丰富的饭啊，必然是可以减少维系成本的。 进而想到的是，一旦你认为打篮球是为了保持身体健康，就像跑步一样，那就可能不会去打球了吧，打球就已经变成了一项需要去「完成」的任务而已。那健身也是啊，觉得这就是一件为了身体健康而完成任务的事情，那就肯定不会那么容易开始了。把这样的事情变成爱好和享受，就肯定不会那么痛苦了吧。 ## 何为平庸？ 然后更加让人忧伤的是，为什么这样子就是走向平庸呢？我做饭，我跟家庭孩子快乐相处，怎么就变成了世人眼中的平庸？我享受平凡的生活又怎么了我是感到幸福的啊。换个角度来说，到底怎么样的人生才是不平庸的？是不是一定要成为国家领导人，著名画家，发送神舟飞船的那个人才一定伟大呢？如果作为一名厨师，世人对其的眼光就一定是没有价值，或者说价值比不上操控飞船，金融交易的人了吗？ 职业有高低，人也一定要往高处走，成为人上人，那为什么就不能够每个人都去做自己真正想做的事情，放弃这么些所谓的财富、权势？从小时候开始，我们就想着成为政治家、科学家，成为一个国家栋梁影响世界的人。而国外的小朋友也许会说我将来想成为一名兽医、消防员、甚至农民，可是又有谁觉得这样的职业就不够高大上呢？ > [你必须按照别人的看法，按照社会的规则去过你自己的生活。](http://www.zhihu.com/question/34567780/answer/59930815) 我一直期望的就是，教育最终目的不是让人成为人上人，而是让每个孩子都能成为自己想成为的样子。 可悲的就是人性，人总是被利益驱使着而不断向上吧。哪怕中国的义务教育已经推行到了初中，可从小学开始，依旧有太多的家长把孩子送到私立学校，哪怕学费再贵冲破脑袋也要进去。家长总是期望孩子能站在一个更高的起点，比自己过得好，成为人上人。而每个孩子被 push 着，直到步入职场，依旧想着成为人上人，有着一个改变世界的梦想。一直在被定义着，按照世上已经安排好的路一直走着。 ## 何为梦想？ 也不知道自己这样做到底如何？始终还是要做一个有梦想的人吧，刚刚开始工作就被工作的事情充斥了所有的生活，可能到最后也会冲掉自己的梦想。然而我也对梦想不够清晰了，改变世界，呵呵，我该从哪里开始？我现在做的事情又会对这样的梦想产生何种影响。 也许吧，如果梦想是当一名画家，那我现在就去画画就好了；如果我想成为一名歌手，那我每天练歌也就算是走在了奔向梦想的路上。那如果我想改变世界，而我却在敲打键盘，我到底在做什么才能使这个世界更加美好。我并没有什么点子能直接改变心目中的那群年轻人，依旧每个人都在过着自己的一如既往，我的工作的意义根本看不到。 让我更加难以释怀的是，我终究只是成为了一个比别人过得好点的「普通人」，而已。 ## 关于教育 教育的方式到底是怎么样的，如果不成为一名商人，我能够成为的或许就是个码农，就是个 PM。但是依旧想贡献出一点点力量，为那个能够影响世界的产品有所付出。但是谁来衡量这个付出的价值，我没有办法。价值意义的检验标准是什么，我并不知道。 如果一直这样找不到意义，我该做些什么，难道就只是维系生活吗？ 从校园到职场，算是完成了人生中第一次重大的角色转换，而在这个质变的转折点上，适应期就真的只能是一段时间，绝不可能让你一直都在适应着，否则何来试用期？而正确的态度是需要将它看做一个新的起点，如何从此开始到达下一个质变的转折点，需要自己去寻找。也许下次质变是自己出来创业，当然也可能是另外一种形态。总之，期望在那一次拼搏过之后，自己也就不会再后悔，哪怕最后走向了平庸，那又如何？ ## 新的起点 终于算是说服了自己，现在就是一个新的起点，虽然暂且还在适应期。但是该做的事情现在都在慢慢起步之中，自己也将承担越来越多的责任，培养更多的能力。只为下一次「腾飞」的机会吧，就是为了做好准备而努力，没有太多的其他理由。 现在的自己，不用也不应该去想那么多生活上的事情，就开始尽量压缩生活的维系成本吧。从现在开始简化生活，然后把重心放到身体健康、专业知识、职业技能上来。把「不断进步」排在所有这些 maintenance 前面来吧，现在就开始： ## 开源节流 **开源**就是开拓能用于学习进步的时间，用更少的 maitenance 成本，来达到相同甚至同样的维护标准。利用各种生活生产(productivity)工具是其一，比如家电和办公软件，都可以有效节约时间。学会时间管理是其二，比如一周烹饪法（Meal Prep，详见[如何快速做饭？ - 知乎用户的回答](http://www.zhihu.com/question/20059367/answer/39299329)），可以大大减少用在做菜上的精力；也可以设定一天中只有某个时间段登陆邮箱和社交网络，避免沉迷。 **节流**指的是把空隙中的时间都利用起来学习，比如坐地铁时看书，做家务时听 podcast。我个人有少许的拖延症和注意力不集中综合症，而我采取的方法就是用一个任务去拖延另一个任务，于是不知不觉中，虽然我没有完成任务 A，但我已完成了任务 B，而完成任务的成就感会支撑我着手进行下一个任务。这也是斯坦福教授 John Perry 提倡的“结构化拖延法”，得了搞笑诺贝尔奖哟。 via <http://www.zhihu.com/question/33220674/answer/57897678>

zho_Hans

f794bb6996ec15b1773781dc1cabd0daf8316e96

md

Markdown

README.md

abelkartwii/eavesdropper

c4d0030719697149b6ff80c5d5e58cebaec0fc24

README.md

abelkartwii/eavesdropper

c4d0030719697149b6ff80c5d5e58cebaec0fc24

README.md

abelkartwii/eavesdropper

c4d0030719697149b6ff80c5d5e58cebaec0fc24

# Eavesdropper ## Overview This project uses Kafka, Spark, and Flask to analyze and store the sentiments of a Twitter trend in a certain location. Input your location, and receive the sentiment status of the trending topics in your area, as well as the sentiment of it globally! (For developing purposes, I will use Jakarta as my location) ## Workflow #### 1. Ingest Twitter stream (Twitter Streams / Kafka) Using the `tweepy` Python module, tweets from the selected location will be pulled as JSON objects and inserted into an event stream that will be the input to three separate Kafka topics, which are: 1. a topic containing all tweets about the trend made in a certain location that are *geotagged* with precise coordinates (where the user has tweeted with GPS enabled) 2. a topic containing all tweets about the trend made in a certain location 3. a topic containing all tweets about the trend in the location's country, which is used to compare the differences in sentiment between locations. #### 2. Process Kafka topics (Kafka / Spark) The three Kafka topics in the first stage are then processed in this stage using Spark to create dataframes with a running total of tweets. Using the `textblob` Python module, this stage will create a new Kafka event stream (topic) of coordinates and sentiment levels, which will be published to the frontend at 15-second intervals. #### 3. Front-end visualization (to-do) This stage uses Flask to consume data from Spark and the Kafka sentiment event stream. ## Configuration and Setup This project utilizes [Docker](https://docs.docker.com/get-docker/) to create a consistent environment that can deploy the application easily. This project uses both a Dockerfile and Docker Compose. The Dockerfile is an image started from an Alpine image that is used to install Python and Java -- two environments required to run the project's requirements. To build a container, use ``` docker build -t eavesdropper . ``` and then run the built image: ``` docker run -d -p 8080:8080 eavesdropper:latest ``` In order to install the frameworks needed in this project, we will need to use docker-compose to build local images. To do so, run ``` docker-compose up ``` Kafka (and Zookeeper) and Spark will be installed in the container's root directory through this process. ## License This project uses the [MIT license](https://choosealicense.com/licenses/mit/). <!-- Run `eavesdropper.py` in your Spark directory with your desired topic in quotes. This will fetch the data from the Twitter API for Rina Sawayama: ``` python bin/spark-submit eavesdropper.py "Rina Sawayama" ``` This filter will select tweets that mention Rina Sawayama, and the data will be ingested to a Kafka producer. By default, the filter will only search for tweets in English; to change this, change `languages` under `main()` in `main.py` to the language of your choice. **2. Analyze sentiments (PySpark / Kafka)** Run `heartdropper.py`, which will run a sentiment analysis on our selected topic. ``` python heartdropper.py ``` **3. Storage (Cassandra)** to-do... **4. Visualization** to-do... ## ## Configuration The tools used in this project are: * [Python](https://www.python.org/downloads/) 3.9.2 * [Apache Spark](https://spark.apache.org/downloads.html) 3.0.1 (namely PySpark and Spark Streaming) * [Apache Kafka](https://kafka.apache.org/downloads) 2.7.0 * [Apache Cassandra](https://cassandra.apache.org/download/) 3.11 * [Twitter Stream API](https://developer.twitter.com/) The required Python Required Python modules: `pykafka`, `tweepy`, `textblob`. To access Twitter data, create a Twitter API account [here](https://developer.twitter.com/en/apply-for-access) first, obtain the necessary keys, and place them in `config.cfg` as below. ``` consumer_key = <insert your consumer key here> consumer_secret = <insert your consumer secret here> access_token = <insert your access token here> access_secret = <insert your access secret here> ``` You will need to start a Kafka server. On the Windows command line, run the following code in your Kafka directory to start the Kafka and Zookeeper servers, and to create the corresponding Kafka `eavesdropper` topic : ``` .\bin\windows\kafka-server-start.bat .\config\server\properties .\bin\windows\zookeeper-server-start.bat .\config\zookeeper.properties .\bin\windows\kafka-topics.bat --create --zookeeper localhost:2181 --replication-factor 1 --partitions 1 --topic <eavesdropper> ``` You will also need to start Cassandra, which can be done by running the following code on the command line in your Cassandra directory: ``` .\bin\cassandra -f ``` ## Approach -->

eng_Latn

f7959ba37a72b0efafac49b95f0eaa56e1f01365

md

Markdown

README.md

dportabella/spark-examples

51744d74b13abfca1a0b54c7ada082a2fe98dc01

2017-10-08T18:44:01.000Z

2021-09-12T15:59:31.000Z

README.md

dportabella/spark-examples

51744d74b13abfca1a0b54c7ada082a2fe98dc01

2016-05-31T14:44:08.000Z

2016-09-02T09:00:43.000Z

README.md

dportabella/spark-examples

51744d74b13abfca1a0b54c7ada082a2fe98dc01

2016-07-30T18:37:32.000Z

2021-05-19T05:44:32.000Z

# spark-examples This project is a mirror of the spark examples (`data` and `examples/src`) from the official spark distribution: https://github.com/apache/spark/tree/v1.6.1 The build.sbt is based on the original pom.xml with some fixes. ## Build and run an example from the shell ``` $ sbt -Dspark.master=local[2] "runMain org.apache.spark.examples.SparkPi 1000" ... [info] Running org.apache.spark.examples.SparkPi 1000 16/07/18 13:13:53 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable Pi is roughly 3.1418342 [success] Total time: 32 s, completed Jul 18, 2016 1:14:20 PM ``` ## Build and run from IntelliJ IntelliJ -> Import project -> [find spark-examples/build.sbt] All the errors should go away once IntelliJ automatically downloads all the dependencies (this takes a while). Menu -> Run -> Edit Configurations -> + -> Application ``` Name: SparkPi Main class: org.apache.spark.examples.SparkPi VM Options: -Dspark.master=local[2] Program parameters: 1000 ``` Menu -> Run -> Run SparkPi ## Assembly jar and run with spark-submit ``` # build target/scala-2.10/spark-examples-assembly-1.6.1.jar $ sbt assembly # launch the example using spark-submit $ $SPARK_HOME/bin/spark-submit --class org.apache.spark.examples.SparkPi --master local[2] target/scala-2.10/spark-examples-assembly-1.6.1.jar 1000 16/07/18 12:55:30 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable Pi is roughly 3.14160476 ``` ## Select the example to run from sbt ``` $ sbt -Dspark.master=local[2] run [info] Loading global plugins from /Users/david/.sbt/0.13/plugins [info] Loading project definition from /Users/david/temp/spark-examples/project [info] Set current project to spark-examples (in build file:/Users/david/temp/spark-examples/) [warn] Multiple main classes detected. Run 'show discoveredMainClasses' to see the list Multiple main classes detected, select one to run: [1] org.apache.spark.examples.DriverSubmissionTest [2] org.apache.spark.examples.streaming.SqlNetworkWordCount [3] org.apache.spark.examples.streaming.QueueStream [4] org.apache.spark.examples.mllib.GradientBoostingRegressionExample [5] org.apache.spark.examples.streaming.DirectKafkaWordCount [6] org.apache.spark.examples.mllib.NaiveBayesExample [7] org.apache.spark.examples.mllib.MulticlassMetricsExample [8] org.apache.spark.examples.ml.SQLTransformerExample [9] org.apache.spark.examples.SimpleSkewedGroupByTest [10] org.apache.spark.examples.mllib.RegressionMetricsExample [11] org.apache.spark.examples.mllib.SampledRDDs [12] org.apache.spark.examples.LogQuery [13] org.apache.spark.examples.mllib.DecisionTreeRunner [14] org.apache.spark.examples.CassandraCQLTest [15] org.apache.spark.examples.ml.RandomForestClassifierExample [16] org.apache.spark.examples.mllib.DenseGaussianMixture [17] org.apache.spark.examples.mllib.SimpleFPGrowth [18] org.apache.spark.examples.LocalKMeans [19] org.apache.spark.examples.graphx.LiveJournalPageRank [20] org.apache.spark.examples.ml.NormalizerExample [21] org.apache.spark.examples.ml.OneVsRestExample [22] org.apache.spark.examples.ml.DCTExample [23] org.apache.spark.examples.streaming.clickstream.PageViewStream [24] org.apache.spark.examples.LocalALS [25] org.apache.spark.examples.ml.StandardScalerExample [26] org.apache.spark.examples.ml.PCAExample [27] org.apache.spark.examples.streaming.SimpleZeroMQPublisher [28] org.apache.spark.examples.streaming.ZeroMQWordCount [29] org.apache.spark.examples.streaming.NetworkWordCount [30] org.apache.spark.examples.streaming.FlumeEventCount [31] org.apache.spark.examples.mllib.DenseKMeans [32] org.apache.spark.examples.mllib.LDAExample [33] org.apache.spark.examples.mllib.CosineSimilarity [34] org.apache.spark.examples.streaming.FeederActor [35] org.apache.spark.examples.streaming.ActorWordCount [36] org.apache.spark.examples.streaming.StatefulNetworkWordCount [37] org.apache.spark.examples.mllib.StreamingLogisticRegression [38] org.apache.spark.examples.DFSReadWriteTest [39] org.apache.spark.examples.SparkALS [40] org.apache.spark.examples.ml.DecisionTreeRegressionExample [41] org.apache.spark.examples.ml.RFormulaExample [42] org.apache.spark.examples.ml.DecisionTreeClassificationExample [43] org.apache.spark.examples.mllib.MovieLensALS [44] org.apache.spark.examples.mllib.RandomRDDGeneration [45] org.apache.spark.examples.CassandraTest [46] org.apache.spark.examples.mllib.RandomForestClassificationExample [47] org.apache.spark.examples.ml.RandomForestExample [48] org.apache.spark.examples.GroupByTest [49] org.apache.spark.examples.streaming.FlumePollingEventCount [50] org.apache.spark.examples.mllib.RankingMetricsExample [51] org.apache.spark.examples.ml.IndexToStringExample [52] org.apache.spark.examples.ml.KMeansExample [53] org.apache.spark.examples.mllib.PrefixSpanExample [54] org.apache.spark.examples.mllib.GradientBoostedTreesRunner [55] org.apache.spark.examples.ml.StringIndexerExample [56] org.apache.spark.examples.ml.DataFrameExample [57] org.apache.spark.examples.mllib.MultiLabelMetricsExample [58] org.apache.spark.examples.ml.ElementwiseProductExample [59] org.apache.spark.examples.SkewedGroupByTest [60] org.apache.spark.examples.mllib.IsotonicRegressionExample [61] org.apache.spark.examples.ml.QuantileDiscretizerExample [62] org.apache.spark.examples.mllib.BinaryClassificationMetricsExample [63] org.apache.spark.examples.streaming.clickstream.PageViewGenerator [64] org.apache.spark.examples.streaming.TwitterAlgebirdHLL [65] org.apache.spark.examples.mllib.DecisionTreeClassificationExample [66] org.apache.spark.examples.ml.GradientBoostedTreeClassifierExample [67] org.apache.spark.examples.ml.ChiSqSelectorExample [68] org.apache.spark.examples.graphx.SynthBenchmark [69] org.apache.spark.examples.mllib.LBFGSExample [70] org.apache.spark.examples.mllib.TallSkinnySVD [71] org.apache.spark.examples.ml.AFTSurvivalRegressionExample [72] org.apache.spark.examples.ml.SimpleParamsExample [73] org.apache.spark.examples.LocalPi [74] org.apache.spark.examples.mllib.StreamingLinearRegression [75] org.apache.spark.examples.streaming.HdfsWordCount [76] org.apache.spark.examples.ml.GradientBoostedTreeRegressorExample [77] org.apache.spark.examples.mllib.SparseNaiveBayes [78] org.apache.spark.examples.SparkHdfsLR [79] org.apache.spark.examples.mllib.BinaryClassification [80] org.apache.spark.examples.mllib.AssociationRulesExample [81] org.apache.spark.examples.ml.VectorSlicerExample [82] org.apache.spark.examples.HdfsTest [83] org.apache.spark.examples.ml.BucketizerExample [84] org.apache.spark.examples.mllib.StreamingTestExample [85] org.apache.spark.examples.streaming.RecoverableNetworkWordCount [86] org.apache.spark.examples.streaming.TwitterAlgebirdCMS [87] org.apache.spark.examples.mllib.LinearRegression [88] org.apache.spark.examples.MultiBroadcastTest [89] org.apache.spark.examples.ml.CountVectorizerExample [90] org.apache.spark.examples.ml.LinearRegressionExample [91] org.apache.spark.examples.ml.SimpleTextClassificationPipeline [92] org.apache.spark.examples.streaming.TwitterPopularTags [93] org.apache.spark.examples.ml.NGramExample [94] org.apache.spark.examples.LocalLR [95] org.apache.spark.examples.HBaseTest [96] org.apache.spark.examples.SparkPi [97] org.apache.spark.examples.ml.StopWordsRemoverExample [98] org.apache.spark.examples.ml.RandomForestRegressorExample [99] org.apache.spark.examples.graphx.Analytics [100] org.apache.spark.examples.streaming.CustomReceiver [101] org.apache.spark.examples.SparkPageRank [102] org.apache.spark.examples.ml.BinarizerExample [103] org.apache.spark.examples.mllib.GradientBoostingClassificationExample [104] org.apache.spark.examples.mllib.Correlations [105] org.apache.spark.examples.mllib.DecisionTreeRegressionExample [106] org.apache.spark.examples.ml.LDAExample [107] org.apache.spark.examples.SparkLR [108] org.apache.spark.examples.ml.LogisticRegressionWithElasticNetExample [109] org.apache.spark.examples.SparkTC [110] org.apache.spark.examples.ml.TokenizerExample [111] org.apache.spark.examples.ml.LinearRegressionWithElasticNetExample [112] org.apache.spark.examples.mllib.RandomForestRegressionExample [113] org.apache.spark.examples.mllib.PowerIterationClusteringExample [114] org.apache.spark.examples.SparkKMeans [115] org.apache.spark.examples.mllib.StreamingKMeansExample [116] org.apache.spark.examples.SparkTachyonHdfsLR [117] org.apache.spark.examples.ml.TrainValidationSplitExample [118] org.apache.spark.examples.ml.GBTExample [119] org.apache.spark.examples.ml.OneHotEncoderExample [120] org.apache.spark.examples.ml.VectorIndexerExample [121] org.apache.spark.examples.SparkTachyonPi [122] org.apache.spark.examples.sql.RDDRelation [123] org.apache.spark.examples.mllib.BisectingKMeansExample [124] org.apache.spark.examples.sql.hive.HiveFromSpark [125] org.apache.spark.examples.streaming.MQTTPublisher [126] org.apache.spark.examples.streaming.MQTTWordCount [127] org.apache.spark.examples.mllib.MultivariateSummarizer [128] org.apache.spark.examples.ml.MovieLensALS [129] org.apache.spark.examples.ml.LogisticRegressionExample [130] org.apache.spark.examples.mllib.TallSkinnyPCA [131] org.apache.spark.examples.ml.DecisionTreeExample [132] org.apache.spark.examples.ml.PolynomialExpansionExample [133] org.apache.spark.examples.ml.LogisticRegressionSummaryExample [134] org.apache.spark.examples.ml.MultilayerPerceptronClassifierExample [135] org.apache.spark.examples.ml.CrossValidatorExample [136] org.apache.spark.examples.ml.MinMaxScalerExample [137] org.apache.spark.examples.streaming.KafkaWordCount [138] org.apache.spark.examples.streaming.KafkaWordCountProducer [139] org.apache.spark.examples.mllib.FPGrowthExample [140] org.apache.spark.examples.mllib.RecommendationExample [141] org.apache.spark.examples.ml.DeveloperApiExample [142] org.apache.spark.examples.BroadcastTest [143] org.apache.spark.examples.ml.Word2VecExample [144] org.apache.spark.examples.ml.TfIdfExample [145] org.apache.spark.examples.streaming.RawNetworkGrep [146] org.apache.spark.examples.LocalFileLR [147] org.apache.spark.examples.ExceptionHandlingTest [148] org.apache.spark.examples.ml.VectorAssemblerExample Enter number: 96 [info] Running org.apache.spark.examples.SparkPi 16/07/18 13:15:36 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable Pi is roughly 3.1412 [success] Total time: 38 s, completed Jul 18, 2016 1:15:45 PM ```

eng_Latn

f796a2b56efc1d7f4e29f72330ce01273d4c39f8

md

Markdown

_posts/2019-08-06-lattice.md

wffx/wffx.github.io

5e848067162c2c4e560db46075ae00f69db19558

_posts/2019-08-06-lattice.md

wffx/wffx.github.io

5e848067162c2c4e560db46075ae00f69db19558

_posts/2019-08-06-lattice.md

wffx/wffx.github.io

5e848067162c2c4e560db46075ae00f69db19558

--- layout: post title: "密码学学习总结（二）" date: 2019-08-06 categories: cryptography lang: zh excerpt_separator: <!--more--> --- 本文主要分享一下，自己读研两年的关于密码学学习的一些思考和体会。（未完，格密码学篇） <!--more--> ## 前言 我在第一篇写到过，secret sharing想发好的文章越来越难了，当时一度走了很多弯路，最后也没有很好想法。也逐渐意识到，这条路不太好走。 研一的时候，自己无聊时，会经常看其他牛组的科研主页，看的最多的两个组，就是Stanford的Boneh组还有MIT的CSAIL组，你能在他们组看到他们的研究方向和成果，基本上我后来看的一大部分文章都和这两个组有直接或者间接的关系，也是从那时起开始接触了解到后量子密码学(Post-quantum cryptography)。 简而言之，现有的大数分解，离散对数，二次剩余难题等都有多项式时间内的量子算法去破解，所以当前密码学研究的一大热点就是寻找能够抵御量子算法的数学难题，并构造相应的密码系统。 其中个人觉得目前最有前途的两个方向，一是lattice cryptography，二是isogeny cryptography。前者是我后来看文章的主体方向。后者，曾经去了解过，搞的那一套是椭圆曲线上各种模同态之类的，和之前密码学课上的椭圆曲线加解密算法完全不是一个概念，别说introduction了，abstract看的都费劲，而且这方面文章还不是很多，坑还很多，奈何自己数学功底太差，缺的代数知识太多，搞不懂。 ## 格密码 这部分本来是想介绍一些格的基本理论的，后来想想这方面的survey这么多，还是不多费口舌了，另外讲清楚得敲很多公式，markdown实际显示效果也不如latex，就不费劲折腾了。下面大概说下，我的学习经历和过程，给后来人一个建议。 ### 格密码基础 这一阶段，主要学习格的定义和一些基本知识，比如：格基约化，LLL算法，SVP难题，SIVP难题之类的。这部分我推荐两本书，一本是UTM系列中的An Introduction to Mathematical Cryptography，有一章节专门介绍Lattice的。写的通俗易通。另外一本书是Lattice-based Cryptography，作者是Daniele Micciancio和Oded Regev。你看早期2000-2010年间的格密码文章能经常看到这两人的身影。这本书我是跳着看的，没有全看完。 ### 现代的格密码基础 现今看到的大部分格密码相关的方案主要是依赖于Learning with Errors (LWE), Short Integer Solution (SIS)难题，后来有了环上推广的版本，Ring-LWE和Ring-SIS。这些难题的提出，主要是因为早期SVP,SIVP是worst case下难题，需要用额外的技巧，来提出新的难题，使得能从worst case规约到average case。这部分的工作主要集中在2000年到2008年间。主要的成果也是SIS和LWE的提出。关于其中的规约一直读的一直半解，实在惭愧。 了解了基本概念后，强烈建议阅读Peikert的[survey](https://web.eecs.umich.edu/~cpeikert/pubs/lattice-survey.pdf),能节约你的大量时间去了解很多细枝末节的构造方案技巧，对现代的格密码方案有个初步的认识。期间除了看这边survey外，也看了很多关于lattice的报告ppt，有的时候看这些论文会太形式化，看这些ppt会比较简洁，有的时候还会有例子说明，能帮助理解。这篇survey花了我很长时间，尤其是到Ring-LWE和Ring-SIS时，我又去找了原论文阅读，恶补了一波代数知识,才勉强搞明白。但是，时至今日，On Ideal Lattices and Learning with error over rings_full version和On Lattices, Learning with Errors, Random Linear codes, and Cryptography这两篇文章里的，LWE规约和Ring-LWE规约还是看不懂。就大概不那么严谨的能明白为什么LWE和Ring-LWE是难的。 此外，你如果认真去读这篇survey的话，就又会去看些复杂度理论，不可区分性的形式化定义，零知识的证明的一些arguments，甚至是安全两方计算和多方计算的一些基本概念和经典方案。总之这部分，是我觉得读这篇survey另一大收获。后来偶然在知乎上看到有人罗列了一个密码学书单，看完后深有体会。附上[链接](https://zhuanlan.zhihu.com/p/60604123). ## 全同态加密 这玩意真是又爱又恨。。。（待续）

yue_Hant

f79729a7ef80f1ade60ca9f33546a136341c6b75

md

Markdown

OPTIONS.md

adminV/juggle

e0ecbb3ca2fd76e81a675caaaf036f6f11c4e656

2019-10-16T12:27:40.000Z

2022-03-02T03:30:24.000Z

OPTIONS.md

adminV/juggle

e0ecbb3ca2fd76e81a675caaaf036f6f11c4e656

2021-02-27T19:49:59.000Z

2022-02-27T23:19:57.000Z

OPTIONS.md

adminV/juggle

e0ecbb3ca2fd76e81a675caaaf036f6f11c4e656

2019-11-11T00:46:51.000Z

2022-03-08T06:28:53.000Z

## 配置项说明： ### 公共配置： pageName: 页面标题 author: 作者姓名，说明作用，不参与逻辑。 PM: 产品姓名，说明作用，不参与逻辑。 createData: 编辑日期，说明作用，不参与逻辑。 bodyStyle: body容器样式，CSS对象，可为空 pageConfig: 页面结构配置 pageConfig.dataSource 页面数据源，当一个页面多个接口时可为空 pageConfig.dataSource.query 数据源接口参数，可为空 pageConfig.dataSource.baseData 数据源接口配置 pageConfig.dataSource.baseData.originUrl 数据源接口地址 pageConfig.dataSource.baseData.originMethod 数据源接口请求方式 pageConfig.dataSource.baseData.dataKeyChain 数据源接口返回值对应key pageConfig.bodyConfig 页面组件层级结构 styleOptions 出现在各个组件参数中，指代组件样式 dataKeyChain 出现在各个组件参数中，用来关联数据的key，举例： "data,bannerList,0" 等同于 data["bannerList"][0] ### 组件配置： #### BlockSwiper ##### 说明： 轮播组件，基于vant封装。可接受图片，文字等 ##### 用途： 适用于banner元素 ##### 配置项说明： ``` { "templateId": "BlockSwiper", //组件Name一一对应，必填 "prop": { //内部参数 "swiperProp":{ //vant swiper所需所有prop "autoplay": 3000, "duration": 2000, "initial-swipe": 1, "loop": true, }, "swiperType": "img", //轮播类型, img/text，默认img "dataKeyChain": "bannerList", //关联接口数据的key，逗号分割，必填 "styleOptions":{} //容器样式 } } ``` #### BlockImg ##### 说明： 图片块儿 ##### 用途： 懒加载图片库，支持底部文字，顶部文字 ##### 配置项说明： ``` { "templateId": "BlockImg", //组件name "prop": { "text": "天猫", //底部文字 "dataKeyChain": "flexTestData,A", //关联接口数据的key，逗号分割，必填 "styleOptions": {} //自定义容器样式 } } ``` #### BlockImgCard ##### 说明： 图文商品块儿 ##### 用途： 展示商品信息 ##### 配置项说明： ``` { "templateId": "BlockImgCard", "prop": { "dataKeyChain": "", "styleOptions":{} } } ``` #### ContainerFlexBox ##### 说明： flex布局容器 ##### 用途： 作为页面布局使用，支持内嵌各种组件 ##### 配置项说明： ``` { "templateId": "ContainerFlexBox", //模板名称 "prop": { "flexOptions":[ //行数组 { "rowName": "第一行", //说明性质，不起作用 "rowProp":{ //<van-row> props "type": "flex", "justify": "space-around" }, "colProp": {}, //<van-col> props "childItem": [ //子元素，可以包含其他组件 { "templateId": "BlockImg", "prop": { "text": "天猫", "dataKeyChain": "flexTestData,A", } } ] } ], "styleOptions":{ //自定义容器样式 "width": "100%", "top": "-10px", "paddingTop": "10px" } } } ``` #### ContainerTab ##### 说明： tab布局容器 ##### 用途： 标签页切换容器 ##### 配置项说明： ``` { "templateId": "ContainerTab", "prop": { "defaultActive": 0, "tabsProp":{ //tabs组件参数 "background": "#fff", "line-height": "2px", "animated": true, "border": true, "sticky": true, "swipeable": true }, "tabsOptions": [ //选项列表，数组中由几个对象就有几个标签 { "tabTitle": "热卖单品", //tab标题 "childItem": [ //tab内容，可以自由组合 { "templateId": "BlockImg", "prop": { "text": "天猫", "dataKeyChain": "flexTestData,A", } } ], "styleOptions":{} }, { "tabTitle": "热卖单品", //tab标题 "childItem": [ ], "styleOptions":{} } ], "styleOptions":{ "marginTop": "10px" } } } ``` #### ContainerList ##### 说明： list布局容器 ##### 用途： 瀑布流列表容器 ##### 配置项说明： ``` //直接使用顶级数据，需要配置dataKeyChain { "templateId": "ContainerList", "prop": { "listProp":{ //vant list组件prop "loading-text": "加载中...", "finished-text": "", "error-text": "请求失败，刷新页面重新加载", "error.sync": true, }, "dataKeyChain": "listTestData", //数据key "styleOptions":{} }, "childItem":[ //子元素模板 { "templateId": "BlockImgCard", "prop": { "dataKeyChain": "", "styleOptions":{} } } ] } //独立获取数据，需要配置dataSource { "templateId": "ContainerList", "prop": { "listProp":{ "loading-text": "加载中...", "finished-text": "", "error-text": "请求失败，刷新页面重新加载", "error.sync": true, }, "dataSource":{ //数据源 "query": { //查询参数 "publishStatus":"3" }, "origin": { //接口配置 "originUrl": "/mock/0002.json", "originMethod": "get", "dataKeyChain": "listTestData" } }, "styleOptions":{} }, "childItem":[ { "templateId": "BlockImgCard", "prop": { "dataKeyChain": "", "styleOptions":{} } } ] } ``` #### 全局小提示 ##### 说明： fixed布局小块 ##### 用途： 目前仅用作唤起弹窗 ##### 配置项说明： ``` { "templateId": "PublicBubble", "prop": { "bubbleProp":{ "showText": "弹窗测试" //底部文案 }, "dataKeyChain": "flexTestData,A", //图片数据 "styleOptions":{ "bottom": "100px", "right": "0" } } }, ``` #### 全局弹窗 ##### 说明： 全局弹窗组件 ##### 用途： 支持各个方向的页面弹出窗 ##### 配置项说明： ``` { "templateId": "PublicDraw", "prop": { "drawProp":{ //弹窗配置 "position": "left", "closeable": false, "round": false, "close-icon": 'close', "close-on-click-overlay": false, "get-container": "#app" }, "showButton": true, //是否展示页面底部按钮 "successButtonText": "确定", //按钮确认文案 "cancelButtonText": "取消", //按钮取消文案 "drawStyle":{ //弹出窗口样式 "width": "60%", "height": "100%" }, "queryOptions":[ //弹窗内选项 { "queryType": "select", //选择器 "key": "accountType", //绑定到查询参数key "name": "账户名称", //选项name "type": "radio", //单选 "span": "10", //占位 "subItem": [ //选项 { "name": "不限", "value": "-1" }, { "name": "收款", "value": "1" }, { "name": "购车", "value": "2" }, { "name": "日常", "value": "3" } ] } ], "styleOptions":{}, }, "childItem": [ //也支持组件嵌套 { "templateId": "BlockSwiper", "prop": { "swiperProp":{ "autoplay": 3000, "duration": 2000, "initial-swipe": 1, "loop": true, }, "swiperType": "img", "dataKeyChain": "bannerList", "styleOptions":{} } } ] } ```

yue_Hant

f797c5f643ada01959e228951f84043668f167c8

md

Markdown

content/authors/admin/_index.md

rikrixa/rikhiya-ghosh

885e4559610f444798e5c4f8edbae132d94f8fff

content/authors/admin/_index.md

rikrixa/rikhiya-ghosh

885e4559610f444798e5c4f8edbae132d94f8fff

content/authors/admin/_index.md

rikrixa/rikhiya-ghosh

885e4559610f444798e5c4f8edbae132d94f8fff

--- # Display name name: Rikhiya Ghosh # Username (this should match the folder name) authors: - admin # Is this the primary user of the site? superuser: true # Role/position role: PhD Candidate, Computer Science # Organizations/Affiliations organizations: - name: Rensselaer Polytechnic Institute url: "https://www.rpi.edu" # Short bio (displayed in user profile at end of posts) bio: My research interests include computational linguistics, logic, emotions and reasoning. interests: - Phishing and Fraud in Social Networks - Computational Linguistics - Information Retrieval - Logic - Machine Ethics - Emotions and Reasoning education: courses: - course: PhD in Computer Science institution: Rensselaer Polytechnic Institute year: 2019 - course: BE in Computer Science institution: Bengal Engineering and Science University Shibpur (IIEST Shibpur) year: 2010 # Social/Academic Networking # For available icons, see: https://sourcethemes.com/academic/docs/widgets/#icons # For an email link, use "fas" icon pack, "envelope" icon, and a link in the # form "mailto:your-email@example.com" or "#contact" for contact widget. social: - icon: envelope icon_pack: fas link: '#contact' # For a direct email link, use "mailto:test@example.org". #- icon: twitter # icon_pack: fab #link: https://twitter.com/GeorgeCushen - icon: google-scholar icon_pack: ai link: https://scholar.google.co.in/citations?user=0s_HT_4AAAAJ #- icon: github # icon_pack: fab # link: https://github.com/gcushen # Link to a PDF of your resume/CV from the About widget. # To enable, copy your resume/CV to `static/files/cv.pdf` and uncomment the lines below. # - icon: cv # icon_pack: ai # link: files/cv.pdf # Enter email to display Gravatar (if Gravatar enabled in Config) email: "" # Organizational groups that you belong to (for People widget) # Set this to `[]` or comment out if you are not using People widget. user_groups: - Researchers - Visitors --- I am a doctoral candidate in <a href="https://rair.cogsci.rpi.edu">RAIR Lab</a> in <a href="https://science.rpi.edu/computer-science">Computer Science department</a> of <a href="https://www.rpi.edu">Rensselaer Polytechnic Institute</a>. My advisor is <a href="http://homepages.rpi.edu/~brings/">Prof. Selmer Bringsjord</a>. and I am funded by <a href="https://rair.cogsci.rpi.edu/projects/muri/">ONR MURI</a>. My dissertation is on Detection of Counter-masquerading using Counteridenticals. I did my Bachelors in <a href="https://www.iiests.ac.in">Indian Institute of Science and Technology Shibpur</a> in Computer Science.

eng_Latn

f797f35ca09a6489fe3c3134673137f623643739

md

Markdown

README.md

szokebarnabas/akkademy-db

8ced8ed830fe5880832cddf2f928ca479b639732

README.md

szokebarnabas/akkademy-db

8ced8ed830fe5880832cddf2f928ca479b639732

README.md

szokebarnabas/akkademy-db

8ced8ed830fe5880832cddf2f928ca479b639732

# akkademy-db Distributed in-memory database built on Scala and Akka

eng_Latn

f798364a32963fecbcea0d1f30e15cceec91eda9

md

Markdown

2018-10/2018-10-31_short.md

admariner/trending_archive

ffca6522c4fdaa5203c3f18d9a5a7d7da098169c

2015-02-13T16:52:22.000Z

2022-03-10T20:13:08.000Z

2018-10/2018-10-31_short.md

admariner/trending_archive

ffca6522c4fdaa5203c3f18d9a5a7d7da098169c

2021-10-02T05:54:01.000Z

2021-12-28T22:50:23.000Z

2018-10/2018-10-31_short.md

admariner/trending_archive

ffca6522c4fdaa5203c3f18d9a5a7d7da098169c

2015-10-08T11:06:28.000Z

2021-06-30T07:26:49.000Z

### 2018-10-31 diff between today and yesterday #### python * [google-research/bert](https://github.com/google-research/bert): TensorFlow code and pre-trained models for BERT * [codertimo/BERT-pytorch](https://github.com/codertimo/BERT-pytorch): Google AI 2018 BERT pytorch implementation * [ageitgey/face_recognition](https://github.com/ageitgey/face_recognition): The world's simplest facial recognition api for Python and the command line * [ansible/ansible](https://github.com/ansible/ansible): Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy. Avoid writing scripts or custom code to deploy and update your applications automate in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com/ansible/ * [home-assistant/home-assistant](https://github.com/home-assistant/home-assistant): Open source home automation that puts local control and privacy first #### go * [github/orchestrator](https://github.com/github/orchestrator): MySQL replication topology management and HA * [twitchtv/twirp](https://github.com/twitchtv/twirp): A simple RPC framework with protobuf service definitions * [Azure/kubernetes-policy-controller](https://github.com/Azure/kubernetes-policy-controller): kubernetes-policy-controller * [Drakirus/go-flutter-desktop-embedder](https://github.com/Drakirus/go-flutter-desktop-embedder): A Go (golang) Custom Flutter Engine Embedder for desktop * [src-d/go-mysql-server](https://github.com/src-d/go-mysql-server): An extensible MySQL server implementation in Go. * [google/go-write](https://github.com/google/go-write): Package write provides a way to atomically create or replace a file or symbolic link. * [astaxie/build-web-application-with-golang](https://github.com/astaxie/build-web-application-with-golang): A golang ebook intro how to build a web with golang * [replicatedhq/ship](https://github.com/replicatedhq/ship): Reducing the Operational Overhead of Maintaining 3rd-party Applications in Kubernetes * [mercari/yo](https://github.com/mercari/yo): * [go-gitea/gitea](https://github.com/go-gitea/gitea): Git with a cup of tea, painless self-hosted git service * [akiyosi/gonvim](https://github.com/akiyosi/gonvim): Neovim GUI written in Golang, using a Golang qt backend #### cpp * [google/flutter-desktop-embedding](https://github.com/google/flutter-desktop-embedding): Desktop implementations of the Flutter embedding API * [monadgroup/axiom](https://github.com/monadgroup/axiom): A powerful realtime node-based audio synthesizer. * [Microsoft/EdgeML](https://github.com/Microsoft/EdgeML): This repository provides code for machine learning algorithms for edge devices developed at Microsoft Research India. * [rathena/rathena](https://github.com/rathena/rathena): rAthena is an open-source cross-platform MMORPG server. * [ValveSoftware/Proton](https://github.com/ValveSoftware/Proton): Compatibility tool for Steam Play based on Wine and additional components * [energicryptocurrency/energi](https://github.com/energicryptocurrency/energi): Cryptocurrency for world adoption. * [uglide/RedisDesktopManager](https://github.com/uglide/RedisDesktopManager): Cross-platform GUI management tool for Redis #### javascript * [skidding/jobs-done](https://github.com/skidding/jobs-done): Ritual app for ending the work day inspired by Deep Work * [GoogleChromeLabs/carlo](https://github.com/GoogleChromeLabs/carlo): Web rendering surface for Node applications * [Tencent/westore](https://github.com/Tencent/westore): - 1KB javascript * [victorqribeiro/invaderz](https://github.com/victorqribeiro/invaderz): Space invaders, but the invaders evolve with genetic algorithm * [sarahdayan/dinero.js](https://github.com/sarahdayan/dinero.js): An immutable library to create, calculate and format money. * [kaola-fed/megalo](https://github.com/kaola-fed/megalo): Vue * [posva/vue-promised](https://github.com/posva/vue-promised): Promises as components #### coffeescript * [kucherenko/jscpd](https://github.com/kucherenko/jscpd): Copy/paste detector for programming source code. * [viruschidai/diff-json](https://github.com/viruschidai/diff-json): A javascript object diff tool * [adaltas/node-csv-parse](https://github.com/adaltas/node-csv-parse): CSV parsing implementing the Node.js `stream.Transform` API * [nicolaskruchten/pivottable](https://github.com/nicolaskruchten/pivottable): Open-source Javascript Pivot Table (aka Pivot Grid, Pivot Chart, Cross-Tab) implementation with drag'n'drop. * [Glavin001/atom-beautify](https://github.com/Glavin001/atom-beautify): Universal beautification package for Atom editor ( Currently migrating to https://github.com/Unibeautify/ and have very limited bandwidth for Atom-Beautify Issues. Thank you for your patience and understanding )

eng_Latn

f79907b9ebf62322f9a46cd7ddce076b6da82287

md

Markdown

4-js-or-jsx-template/readme.md

vahapgencdal/react-tutorial

6c75213a2f55d92a246e9c82fa5a1fb8a0e088d0

2018-09-03T07:08:29.000Z

2018-09-03T07:08:29.000Z

4-js-or-jsx-template/readme.md

vahapgencdal/react-tutorial

6c75213a2f55d92a246e9c82fa5a1fb8a0e088d0

4-js-or-jsx-template/readme.md

vahapgencdal/react-tutorial

6c75213a2f55d92a246e9c82fa5a1fb8a0e088d0

##ReactJS - JSX -JS React uses JSX for templating instead of regular JavaScript. It is not necessary to use it, however, following are some pros that come with it. - It is faster because it performs optimization while compiling code to JavaScript. - It is also type-safe and most of the errors can be caught during compilation. - It makes it easier and faster to write templates, if you are familiar with HTML. ##Content Elements If we want to return more elements, we need to wrap it with one container element. Notice how we are using div as a wrapper for h1, h2 and p elements. ``` import React from 'react'; class Content extends React.Component { render() { return ( <div> <h1>Header</h1> <h2>Content</h2> <p>This is the Content content!!!</p> </div> ); } } export default Content; ``` ##Attributes We can use our own custom attributes in addition to regular HTML properties and attributes. When we want to add custom attribute, we need to use **data-** prefix. In the following example, we added **data-myattribute** as an attribute of **p** element. ``` import React from 'react'; class Header extends React.Component{ render(){ return(<div> <p data-myattribute = "somevalue">This is the Custom Header!!! Inspect and Look source</p> </div>); } } export default Header; ``` ##JavaScript Expressions JavaScript expressions can be used inside of JSX. We just need to wrap it with curly brackets {}. The following example will render 6. We cannot use if else statements inside JSX, instead we can use conditional (ternary) expressions. ``` import React from 'react'; class Home extends React.Component{ render(){ const i=1; return(<div> <p> {2*3} </p> <p> {/*if(i==1)'True'else'False' Give error*/} {i==1?'True':'False'} </p> </div>); } } export default Home; ``` ##Styling React recommends using inline styles. When we want to set inline styles, we need to use camelCase syntax. React will also automatically append px after the number value on specific elements. The following example shows how to add myStyle inline to h1 element. ``` import React from 'react'; class Styling extends React.Component{ render(){ var customStyle = { fontSize: 100, color: '#FF0000' }; return ( <div> <h1 style = {customStyle}>Header</h1> </div> ); } } export default Styling; ``` ##Comments When writing comments, we need to put curly brackets **{}** when we want to write comment within children section of a tag. It is a good practice to always use {} when writing comments, since we want to be consistent when writing the app. ``` import React from 'react'; class Styling extends React.Component{ render(){ var customStyle = { fontSize: 100, color: '#FF0000' }; return ( <div> <h1 style = {customStyle}>Header</h1> </div> ); } } export default Styling; ``` ##Naming Convention HTML tags always use **lowercase** tag names, while React components start with **Uppercase**. Note − You should use **className** and **htmlFor** as XML attribute names instead of **class** and **for**.

eng_Latn

f79914202b70d3ab33d1787207ea0d3810356806

md

Markdown

NEWS.md

schifferl/tuberculosis.pipeline

653c489fc7e5b3de13b4b6d7e3a55b490381487e

2021-11-04T14:53:14.000Z

2021-11-04T14:53:14.000Z

NEWS.md

schifferl/tuberculosis.pipeline

653c489fc7e5b3de13b4b6d7e3a55b490381487e

NEWS.md

schifferl/tuberculosis.pipeline

653c489fc7e5b3de13b4b6d7e3a55b490381487e

# tuberculosis.pipeline 1.0.0 * Gene annotations were updated using the genenames.org REST API on September 1, 2021.

eng_Latn

f799765ce09a5a386c5193e374b2110b09f82ae5

md

Markdown

README.md

salemjoban1/webpage_for_increase_sales_system

d56d6fc3e323ea3ccb38ea223f38049d436f161b

README.md

salemjoban1/webpage_for_increase_sales_system

d56d6fc3e323ea3ccb38ea223f38049d436f161b

README.md

salemjoban1/webpage_for_increase_sales_system

d56d6fc3e323ea3ccb38ea223f38049d436f161b

# webpage_for_increase_sales_system to preview the page use this link: https://salemjoban1.github.io/webpage_for_increase_sales_system/index.html

yue_Hant

f79a3d34d05f6ad76d26dda742041ee6f536dc56

md

Markdown

guide/english/mathematics/eulers-formula/index.md

waleedali430/freeCodeCamp

ec9fffb222f947a9fd2cf94bb6bc43a46576adf3

2020-07-09T10:19:39.000Z

2021-12-06T00:43:23.000Z

guide/english/mathematics/eulers-formula/index.md

ACTKrishanPratapCMA/freeCodeCamp

b24f606847b6192444b606ad0d21cd8dba0ca642

2019-04-25T23:23:57.000Z

2021-07-28T23:18:44.000Z

guide/english/mathematics/eulers-formula/index.md

ACTKrishanPratapCMA/freeCodeCamp

b24f606847b6192444b606ad0d21cd8dba0ca642

2019-05-29T14:58:56.000Z

2019-07-18T03:52:00.000Z

--- title: Eulers Formula --- ## Eulers Formula Eulers Formula is a mathematical identity which states that (for any value of x): e^(ix)=cosx+isinx This is of interest because of the following case: When x=pi, Euler's Formula gives the beautiful identity invovling pi, e, and i. e^(ipi)+1=0, A famous joke for mathematicians is "How many mathematicians does it take to change a light bulb?" and answers "-e^(ipi)" Can you tell what the answer is? This is often used when dealing with complex numbers in exponential form.  <!-- The article goes here, in GitHub-flavored Markdown. Feel free to add YouTube videos, images, and CodePen/JSBin embeds --> #### More Information: [Mathworld](http://mathworld.wolfram.com/EulerFormula.html) [Wikipedia](https://en.wikipedia.org/wiki/Euler%27s_formula)

eng_Latn

f79a4b924fb92b87f616c90b39402dcee779ce9c

md

Markdown

_posts/2021-07-08/2021-06-25-I-dont-think-I-can-spread-my-little-Scottish-pussy-any-further-20210625034646118920.md

ipussy/ipussy.github.io

95d19a74e38bb54303cf18057a99a57c783e76bf

_posts/2021-07-08/2021-06-25-I-dont-think-I-can-spread-my-little-Scottish-pussy-any-further-20210625034646118920.md

ipussy/ipussy.github.io

95d19a74e38bb54303cf18057a99a57c783e76bf

_posts/2021-07-08/2021-06-25-I-dont-think-I-can-spread-my-little-Scottish-pussy-any-further-20210625034646118920.md

ipussy/ipussy.github.io

95d19a74e38bb54303cf18057a99a57c783e76bf

--- title: "I don't think I can spread my little Scottish pussy any further 🥺" metadate: "hide" categories: [ God Pussy ] image: "https://preview.redd.it/bvq25bxdi9771.jpg?auto=webp&s=1b3365c6c02f2878690bc88d0a578b8a69bef7ad" thumb: "https://preview.redd.it/bvq25bxdi9771.jpg?width=640&crop=smart&auto=webp&s=5c3e01dcec0abcdb25f40067541e6dcbe42c64fd" visit: "" --- I don't think I can spread my little Scottish pussy any further 🥺

yue_Hant

f79a5fdf96137cd778fabc7e22d5f2d0a293963a

md

Markdown

community/renmada/sshleifer-tiny-distilbert-base-uncased-finetuned-sst-2-english/REAMME.md

tanhanzhuo/PaddleNLP

d0d20678f2bec820570b4f09ca49cd402d20c3b6

2021-02-05T13:56:25.000Z

2022-03-31T11:42:50.000Z

community/renmada/sshleifer-tiny-distilbert-base-uncased-finetuned-sst-2-english/REAMME.md

tanhanzhuo/PaddleNLP

d0d20678f2bec820570b4f09ca49cd402d20c3b6

2021-02-10T01:09:29.000Z

2022-03-31T12:12:58.000Z

community/renmada/sshleifer-tiny-distilbert-base-uncased-finetuned-sst-2-english/REAMME.md

tanhanzhuo/PaddleNLP

d0d20678f2bec820570b4f09ca49cd402d20c3b6

2021-02-05T14:26:48.000Z

2022-03-31T11:42:57.000Z

# 模型介绍 tiny-distilbert-base-uncased在sst-2上finetune后的模型 # 模型来源 https://huggingface.co/sshleifer/tiny-distilbert-base-uncased-finetuned-sst-2-english # 模型使用 ```python import paddle from paddlenlp.transformers import DistilBertForSequenceClassification, DistilBertTokenizer model = DistilBertForSequenceClassification.from_pretrained('renmada/sshleifer-tiny-distilbert-base-uncase-finetuned-sst-2-english') tokenizer = DistilBertTokenizer.from_pretrained('renmada/sshleifer-tiny-distilbert-base-uncase-finetuned-sst-2-english') inp = 'It is good' ids = tokenizer.encode(inp)['input_ids'] ids = paddle.to_tensor([ids]) model.eval() with paddle.no_grad(): logtis = model(ids) ```

eng_Latn

f79bed9346058dd3cf0cc47282f3b9af0310e4f7

md

Markdown

doc/func.md

FelixLee1995/Jupiter

90db14069f121248d392aeb1bb9f60a4d0175f93

2021-07-14T17:05:16.000Z

2021-07-14T17:05:16.000Z

doc/func.md

FelixLee1995/Jupiter

90db14069f121248d392aeb1bb9f60a4d0175f93

doc/func.md

FelixLee1995/Jupiter

90db14069f121248d392aeb1bb9f60a4d0175f93

2021-07-15T06:23:15.000Z

2021-07-15T06:23:15.000Z

# 实现的功能 * 多tcp, udp 输入 * 多tcp, udp 输出 * 支持线程池拓展选项 ## 第一步 + 实现config服务， 采用配置文件读取， 或配置中心读取 两种方式 yaml nacos + 实现log服务， 日志和std同时输出， 可配置的级别， 运行时控制 + 插件化加载服务 + 版本更新打包， 更新说明 ## 预计集成的服务 + redis + nacos + mysql/oracle + mongodb + mq 消息队列

yue_Hant

f79c7b03a1d06741c88ff386db682299cf988b0c

md

Markdown

2020/09/26/2020-09-26 09:05.md

zhzhzhy/WeiBoHot_history

32ce4800e63f26384abb17d43e308452c537c902

2020-07-14T14:54:15.000Z

2020-08-21T06:48:24.000Z

2020/09/26/2020-09-26 09:05.md

zhzhzhy/WeiBoHot_history

32ce4800e63f26384abb17d43e308452c537c902

2020/09/26/2020-09-26 09:05.md

zhzhzhy/WeiBoHot_history

32ce4800e63f26384abb17d43e308452c537c902

2020年09月26日09时数据 Status: 200 1.昆凌侯佩岑 彩虹图 微博热度:3332041 2.希腊前财长也太了解中国了 微博热度:2175040 3.NISSAN焕新 微博热度:2075346 4.王俊凯杜海涛同款水壶 微博热度:1791600 5.邓超微博热评第一 微博热度:1341546 6.万科新裤子合作出单曲 微博热度:1224453 7.印度民众轮流吸蒸汽防治新冠 微博热度:1041306 8.这才是家长群该有的样子 微博热度:930652 9.特朗普计划提名巴雷特任最高法院大法官 微博热度:930572 10.微信绑定银行卡可免输卡号 微博热度:917103 11.江阳遗言 微博热度:900717 12.玄彬童年照 微博热度:896598 13.六旬教授喝完秋天第一杯奶茶进了医院 微博热度:885499 14.世卫重申新冠病毒来自自然界 微博热度:877735 15.外卖小哥追回追肇事逃逸者 微博热度:858575 16.百花奖 微博热度:848399 17.林依轮状态 微博热度:847469 18.青岛港组织全体职工核酸检测 微博热度:842602 19.乌克兰一军机坠毁 微博热度:841942 20.马云19年前保密项目重启 微博热度:841518 21.天官赐福 微博热度:841474 22.滔博回应 微博热度:627866 23.2小孩为拍短视频铁轨上逼停动车 微博热度:615574 24.灵儿的采访 微博热度:480079 25.白宇换头像告别江阳 微博热度:467815 26.高校送学生数学分析教程月饼 微博热度:467106 27.姜云升 微博热度:466738 28.赵薇 捍卫家庭的题材该out了 微博热度:448111 29.姜子牙 微博热度:299462 30.张雷争议判罚 微博热度:261828 31.亲爱的自己 微博热度:256368 32.朴宰范英语 微博热度:251360 33.易烊千玺回头杀 微博热度:243958 34.盐城首次发现超千只小青脚鹬 微博热度:234618 35.美国将对非移民签证逗留时间设限 微博热度:226527 36.银行办事窗口被指像墓碑 微博热度:221976 37.彭昱畅工具人 微博热度:219529 38.流苏 微博热度:204774 39.美国新冠肺炎超702万例 微博热度:203547 40.万妮达摸GALI胸肌 微博热度:200814 41.天安门广场祝福祖国花篮亮灯 微博热度:182097 42.餐厅服务员秒换桌布 微博热度:177222 43.从3句话里面找到唯一的假话 微博热度:171426 44.吴奇隆王耀庆带猪度假 微博热度:151108 45.林大厨对王俊凯的长辈式关爱 微博热度:150501 46.中餐厅 微博热度:150113 47.元气满满的哥哥 微博热度:128014 48.林教练现场采访回应 微博热度:121578 49.大连警方通报无牌车与救护车对峙 微博热度:119095 50.刘闻钦人设 微博热度:111339

yue_Hant

f79c7b1dfc14da3d43e9f62dd83f6c31ba67f74b

md

Markdown

README.md

textcreationpartnership/A40439

5ca256f5aa34f3005dd3651ef13581e45a1490d5

README.md

textcreationpartnership/A40439

5ca256f5aa34f3005dd3651ef13581e45a1490d5

README.md

textcreationpartnership/A40439

5ca256f5aa34f3005dd3651ef13581e45a1490d5

#The life of Dom John de Castro, the fourth vice-roy of India wherein are seen the Portuguese's voyages to the East-Indies, their discoveries and conquests there, the form of government, commerce, and discipline of warr in the east, and the topography of all India and China : containing also a particular relation of the most famous siege of Dio, with a map to illustrate it / by Jacinto Freire de Andrada, written in Portuguese ; and by Sr Peter Wyche, Kt., translated into English. Vida de Dom João de Castro, quarto viso-rey da India. English# ##Freire de Andrade, Jacinto, 1597-1657.## The life of Dom John de Castro, the fourth vice-roy of India wherein are seen the Portuguese's voyages to the East-Indies, their discoveries and conquests there, the form of government, commerce, and discipline of warr in the east, and the topography of all India and China : containing also a particular relation of the most famous siege of Dio, with a map to illustrate it / by Jacinto Freire de Andrada, written in Portuguese ; and by Sr Peter Wyche, Kt., translated into English. Vida de Dom João de Castro, quarto viso-rey da India. English Freire de Andrade, Jacinto, 1597-1657. ##General Summary## **Links** [TCP catalogue](http://www.ota.ox.ac.uk/tcp/) • [HTML](http://tei.it.ox.ac.uk/tcp/Texts-HTML/free/A40/A40439.html) • [EPUB](http://tei.it.ox.ac.uk/tcp/Texts-EPUB/free/A40/A40439.epub) • [Page images (Historical Texts)](https://data.historicaltexts.jisc.ac.uk/view?pubId=eebo-12251553e&pageId=eebo-12251553e-57115-1) **Availability** This keyboarded and encoded edition of the work described above is co-owned by the institutions providing financial support to the Early English Books Online Text Creation Partnership. This Phase I text is available for reuse, according to the terms of Creative Commons 0 1.0 Universal. The text can be copied, modified, distributed and performed, even for commercial purposes, all without asking permission. **Major revisions** 1. __2003-09__ __TCP__ *Assigned for keying and markup* 1. __2003-09__ __Aptara__ *Keyed and coded from ProQuest page images* 1. __2003-10__ __Mona Logarbo__ *Sampled and proofread* 1. __2003-10__ __Mona Logarbo__ *Text and markup reviewed and edited* 1. __2003-12__ __pfs__ *Batch review (QC) and XML conversion* ##Content Summary## #####Front##### D. IOAO. DE CASTRO THE FOVRTH VICEROY OF INDIA.portraitW. Faithorne sculp: 1. TO THE QUEENS Most Excellent Majesty. 1. THE Authors Dedication To Prince THE ODOSIUS, Of Happy Memory, Who was Heir of Portugall, and Eldest Brother to Our Most Excellent Queen KATHERINE. 1. THE PREFACE. WHITEHALL, Aug. 12. 1663.Let this Translation be Printed.Henry Bennet. #####Body##### 1. THE LIFE OF DOM IOHN DE CASTRO. 1. THE LIFE OF DOM IOHN DE CASTRO. 1. THE LIFE OF DOM IOHN DE CASTRO. 1. THE LIFE OF DOM IOHN DE CASTRO. #####Back##### 1. An Index of the Most Observable things in this History. By the Composers not current Reading the Copy, some Faults have crept into the Impression; the mista 1. Errata. **Types of content** * There are 172 **verse** lines! * Oh, Mr. Jourdain, there is **prose** in there! There are 200 **ommitted** fragments! @__reason__ (200) : foreign (3), duplicate (8), illegible (187), illegible: missing (1), illegible: blotted (1) • @__extent__ (197) : 1 page (8), 1 letter (152), 2 letters (11), 1 word (15), 4 letters (2), 1 span (8), 3 letters (1) • @__resp__ (187) : #TECH (187) **Character listing** |Text|string(s)|codepoint(s)| |---|---|---| |Latin-1 Supplement|ãèàé½ò|227 232 224 233 189 242| |Combining Diacritical Marks|̄|772| |General Punctuation|•…|8226 8230| |Geometric Shapes|◊▪|9674 9642| |CJKSymbolsandPunctuation|〈〉|12296 12297| ##Tag Usage Summary## ###Header Tag Usage### |No|element name|occ|attributes| |---|---|---|---| |1.|__author__|3|| |2.|__availability__|1|| |3.|__biblFull__|1|| |4.|__change__|5|| |5.|__date__|8| @__when__ (1) : 2004-03 (1)| |6.|__edition__|1|| |7.|__editionStmt__|1|| |8.|__editorialDecl__|1|| |9.|__extent__|2|| |10.|__idno__|6| @__type__ (6) : DLPS (1), STC (2), EEBO-CITATION (1), OCLC (1), VID (1)| |11.|__keywords__|1| @__scheme__ (1) : http://authorities.loc.gov/ (1)| |12.|__label__|5|| |13.|__langUsage__|1|| |14.|__language__|1| @__ident__ (1) : eng (1)| |15.|__listPrefixDef__|1|| |16.|__note__|8|| |17.|__notesStmt__|2|| |18.|__p__|11|| |19.|__prefixDef__|2| @__ident__ (2) : tcp (1), char (1) • @__matchPattern__ (2) : ([0-9\-]+):([0-9IVX]+) (1), (.+) (1) • @__replacementPattern__ (2) : http://eebo.chadwyck.com/downloadtiff?vid=$1&page=$2 (1), https://raw.githubusercontent.com/textcreationpartnership/Texts/master/tcpchars.xml#$1 (1)| |20.|__projectDesc__|1|| |21.|__pubPlace__|2|| |22.|__publicationStmt__|2|| |23.|__publisher__|2|| |24.|__ref__|2| @__target__ (2) : https://creativecommons.org/publicdomain/zero/1.0/ (1), http://www.textcreationpartnership.org/docs/. (1)| |25.|__seriesStmt__|1|| |26.|__sourceDesc__|1|| |27.|__term__|3|| |28.|__textClass__|1|| |29.|__title__|5|| |30.|__titleStmt__|2|| ###Text Tag Usage### |No|element name|occ|attributes| |---|---|---|---| |1.|__abbr__|1|| |2.|__bibl__|11|| |3.|__body__|7|| |4.|__closer__|11|| |5.|__date__|9|| |6.|__dateline__|9|| |7.|__desc__|200|| |8.|__div__|15| @__type__ (15) : frontispiece (1), title_page (1), translators_dedication (1), authors_dedication (1), preface (1), license (1), book (4), letter (2), index (1), notice (1), errata (1) • @__n__ (4) : 1 (1), 2 (1), 3 (1), 4 (1)| |9.|__figDesc__|2|| |10.|__figure__|3|| |11.|__floatingText__|7| @__type__ (5) : letter (5) • @__xml:lang__ (2) : eng (0)| |12.|__g__|1930| @__ref__ (1930) : char:EOLhyphen (1917), char:punc (11), char:cmbAbbrStroke (1), char:EOLunhyphen (1)| |13.|__gap__|200| @__reason__ (200) : foreign (3), duplicate (8), illegible (187), illegible: missing (1), illegible: blotted (1) • @__extent__ (197) : 1 page (8), 1 letter (152), 2 letters (11), 1 word (15), 4 letters (2), 1 span (8), 3 letters (1) • @__resp__ (187) : #TECH (187)| |14.|__head__|178| @__type__ (4) : sub (4)| |15.|__hi__|5272| @__rend__ (13) : sup (13)| |16.|__item__|936|| |17.|__l__|172|| |18.|__lg__|26| @__n__ (18) : 1 (6), 2 (6), 3 (2), 4 (2), 5 (2)| |19.|__list__|138|| |20.|__note__|631| @__n__ (17) : * (10), a (2), b (2), c (1), d (2) • @__place__ (631) : margin (628), bottom (3)| |21.|__opener__|3|| |22.|__p__|468|| |23.|__pb__|319| @__facs__ (319) : tcp:57115:1 (2), tcp:57115:2 (2), tcp:57115:3 (2), tcp:57115:4 (2), tcp:57115:5 (2), tcp:57115:6 (2), tcp:57115:7 (2), tcp:57115:8 (2), tcp:57115:9 (2), tcp:57115:10 (2), tcp:57115:11 (2), tcp:57115:12 (2), tcp:57115:13 (2), tcp:57115:14 (2), tcp:57115:15 (2), tcp:57115:16 (2), tcp:57115:17 (2), tcp:57115:18 (2), tcp:57115:19 (2), tcp:57115:20 (2), tcp:57115:21 (2), tcp:57115:22 (2), tcp:57115:23 (2), tcp:57115:24 (2), tcp:57115:25 (2), tcp:57115:26 (2), tcp:57115:27 (2), tcp:57115:28 (2), tcp:57115:29 (2), tcp:57115:30 (2), tcp:57115:31 (2), tcp:57115:33 (2), tcp:57115:34 (2), tcp:57115:35 (2), tcp:57115:36 (2), tcp:57115:37 (2), tcp:57115:38 (2), tcp:57115:39 (2), tcp:57115:40 (2), tcp:57115:41 (2), tcp:57115:42 (2), tcp:57115:43 (2), tcp:57115:44 (2), tcp:57115:45 (2), tcp:57115:46 (2), tcp:57115:47 (2), tcp:57115:48 (2), tcp:57115:49 (2), tcp:57115:50 (2), tcp:57115:51 (1), tcp:57115:54 (2), tcp:57115:55 (2), tcp:57115:56 (2), tcp:57115:57 (2), tcp:57115:58 (2), tcp:57115:59 (2), tcp:57115:60 (2), tcp:57115:61 (2), tcp:57115:62 (2), tcp:57115:63 (2), tcp:57115:64 (2), tcp:57115:65 (2), tcp:57115:66 (2), tcp:57115:67 (2), tcp:57115:68 (2), tcp:57115:69 (2), tcp:57115:70 (2), tcp:57115:71 (2), tcp:57115:72 (2), tcp:57115:73 (2), tcp:57115:74 (2), tcp:57115:75 (2), tcp:57115:76 (2), tcp:57115:77 (2), tcp:57115:78 (2), tcp:57115:79 (2), tcp:57115:80 (2), tcp:57115:81 (2), tcp:57115:82 (2), tcp:57115:83 (2), tcp:57115:84 (2), tcp:57115:85 (2), tcp:57115:86 (2), tcp:57115:87 (2), tcp:57115:88 (2), tcp:57115:89 (2), tcp:57115:90 (2), tcp:57115:91 (2), tcp:57115:92 (2), tcp:57115:93 (2), tcp:57115:94 (2), tcp:57115:95 (2), tcp:57115:96 (2), tcp:57115:97 (2), tcp:57115:98 (2), tcp:57115:99 (2), tcp:57115:100 (2), tcp:57115:101 (2), tcp:57115:102 (2), tcp:57115:103 (2), tcp:57115:104 (2), tcp:57115:105 (2), tcp:57115:106 (2), tcp:57115:107 (2), tcp:57115:108 (2), tcp:57115:109 (2), tcp:57115:110 (2), tcp:57115:111 (2), tcp:57115:112 (2), tcp:57115:113 (2), tcp:57115:114 (2), tcp:57115:115 (2), tcp:57115:116 (2), tcp:57115:117 (2), tcp:57115:118 (2), tcp:57115:119 (2), tcp:57115:120 (2), tcp:57115:121 (2), tcp:57115:122 (2), tcp:57115:123 (2), tcp:57115:124 (2), tcp:57115:125 (2), tcp:57115:126 (2), tcp:57115:127 (2), tcp:57115:128 (2), tcp:57115:129 (2), tcp:57115:130 (2), tcp:57115:131 (2), tcp:57115:132 (2), tcp:57115:133 (2), tcp:57115:134 (2), tcp:57115:135 (2), tcp:57115:136 (2), tcp:57115:137 (2), tcp:57115:138 (2), tcp:57115:139 (2), tcp:57115:140 (2), tcp:57115:141 (2), tcp:57115:142 (2), tcp:57115:143 (2), tcp:57115:144 (2), tcp:57115:145 (2), tcp:57115:146 (2), tcp:57115:147 (2), tcp:57115:148 (2), tcp:57115:149 (2), tcp:57115:150 (2), tcp:57115:151 (2), tcp:57115:152 (2), tcp:57115:153 (2), tcp:57115:154 (2), tcp:57115:155 (2), tcp:57115:156 (2), tcp:57115:157 (2), tcp:57115:158 (2), tcp:57115:159 (2), tcp:57115:160 (2), tcp:57115:161 (2), tcp:57115:162 (2), tcp:57115:163 (2) • @__rendition__ (1) : simple:additions (1) • @__n__ (274) : 1 (1), 2 (1), 3 (1), 4 (1), 5 (1), 6 (1), 7 (1), 8 (1), 9 (1), 10 (1), 11 (1), 12 (1), 13 (1), 14 (1), 15 (1), 16 (1), 17 (1), 18 (1), 19 (1), 20 (1), 21 (1), 22 (1), 23 (1), 24 (2), 25 (2), 26 (1), 27 (1), 28 (1), 29 (1), 30 (1), 31 (1), 32 (1), 33 (1), 34 (1), 35 (1), 37 (1), 38 (1), 39 (1), 40 (1), 41 (1), 42 (1), 43 (1), 44 (1), 45 (1), 46 (1), 47 (1), 48 (1), 49 (1), 50 (1), 51 (1), 52 (1), 53 (1), 54 (1), 55 (1), 56 (1), 57 (1), 58 (1), 59 (1), 60 (1), 61 (1), 62 (1), 63 (1), 64 (1), 65 (1), 66 (1), 67 (1), 68 (1), 69 (1), 70 (1), 71 (1), 72 (1), 74 (1), 75 (1), 76 (1), 77 (1), 78 (1), 79 (1), 80 (1), 81 (1), 82 (1), 83 (1), 84 (1), 85 (1), 86 (1), 87 (1), 88 (1), 89 (1), 90 (1), 91 (1), 92 (1), 93 (1), 94 (1), 95 (1), 96 (1), 97 (1), 98 (1), 99 (1), 100 (1), 101 (1), 102 (1), 103 (1), 104 (1), 105 (1), 106 (1), 107 (1), 108 (1), 109 (1), 110 (1), 111 (1), 112 (1), 113 (1), 114 (1), 115 (1), 116 (1), 117 (1), 118 (1), 119 (1), 120 (1), 121 (1), 122 (1), 123 (1), 124 (2), 125 (2), 126 (1), 127 (1), 128 (1), 129 (1), 130 (1), 131 (1), 132 (1), 133 (1), 134 (1), 135 (1), 136 (1), 137 (1), 138 (1), 139 (1), 140 (1), 141 (1), 142 (1), 143 (1), 144 (1), 145 (1), 146 (1), 147 (1), 148 (1), 149 (1), 150 (1), 151 (1), 152 (1), 153 (1), 154 (1), 155 (1), 156 (1), 157 (1), 158 (1), 159 (1), 160 (1), 161 (1), 162 (1), 163 (1), 164 (1), 165 (1), 166 (1), 167 (1), 168 (1), 169 (1), 170 (1), 171 (1), 172 (1), 173 (1), 174 (1), 175 (1), 176 (1), 177 (1), 178 (1), 179 (1), 180 (1), 181 (1), 182 (1), 183 (1), 184 (1), 185 (1), 186 (1), 187 (1), 188 (1), 189 (1), 190 (1), 191 (1), 192 (1), 193 (1), 194 (1), 195 (1), 196 (1), 197 (1), 198 (1), 199 (1), 200 (1), 201 (1), 202 (1), 203 (1), 204 (1), 205 (1), 206 (1), 207 (1), 208 (1), 209 (1), 210 (1), 211 (1), 212 (1), 213 (1), 214 (1), 215 (1), 216 (1), 217 (1), 218 (1), 219 (1), 220 (1), 221 (1), 222 (1), 223 (1), 224 (1), 225 (1), 226 (1), 227 (1), 228 (1), 229 (1), 230 (1), 231 (1), 232 (1), 233 (1), 234 (1), 235 (1), 236 (1), 237 (1), 238 (1), 239 (1), 240 (1), 241 (1), 242 (1), 243 (1), 244 (1), 245 (1), 246 (1), 247 (1), 248 (1), 249 (1), 250 (1), 251 (1), 252 (1), 253 (1), 254 (1), 255 (1), 256 (1), 257 (1), 258 (1), 259 (1), 260 (1), 261 (1), 262 (1), 263 (1), 264 (1), 265 (1), 266 (1), 267 (1), 268 (1), 269 (1), 270 (1), 271 (1), 272 (1)| |24.|__q__|24|| |25.|__salute__|3|| |26.|__seg__|7| @__rend__ (7) : decorInit (7)| |27.|__signed__|10|| |28.|__trailer__|2||

eng_Latn

f79d49eb309298ed123238ee1c65228e4dc17366

md

Markdown

articles/active-directory/saas-apps/scalex-enterprise-tutorial.md

KazuOnuki/azure-docs.ja-jp

4dc313dec47a4efdb0258a8b21b45c5376de7ffc

articles/active-directory/saas-apps/scalex-enterprise-tutorial.md

KazuOnuki/azure-docs.ja-jp

4dc313dec47a4efdb0258a8b21b45c5376de7ffc

articles/active-directory/saas-apps/scalex-enterprise-tutorial.md

KazuOnuki/azure-docs.ja-jp

4dc313dec47a4efdb0258a8b21b45c5376de7ffc

--- title: 'チュートリアル: Azure AD SSO と ScaleX Enterprise の統合' description: Azure Active Directory と ScaleX Enterprise の間でシングル サインオンを構成する方法について説明します。 services: active-directory author: jeevansd manager: CelesteDG ms.reviewer: celested ms.service: active-directory ms.subservice: saas-app-tutorial ms.workload: identity ms.topic: tutorial ms.date: 09/29/2021 ms.author: jeedes ms.openlocfilehash: 05fa6eacd489a7071c0f1bcb3d5942e9230fe890 ms.sourcegitcommit: 677e8acc9a2e8b842e4aef4472599f9264e989e7 ms.translationtype: HT ms.contentlocale: ja-JP ms.lasthandoff: 11/11/2021 ms.locfileid: "132308980" --- # <a name="tutorial-azure-ad-sso-integration-with-scalex-enterprise"></a>チュートリアル: Azure AD SSO と ScaleX Enterprise の統合 このチュートリアルでは、ScaleX Enterprise と Azure Active Directory (Azure AD) を統合する方法について説明します。 ScaleX Enterprise と Azure AD を統合すると、次のことができます。 * ScaleX Enterprise にアクセスできるユーザーを Azure AD で制御できます。 * ユーザーが自分の Azure AD アカウントを使用して ScaleX Enterprise に自動的にサインインするように設定できます。 * 1 つの中央サイト (Azure Portal) で自分のアカウントを管理します。 ## <a name="prerequisites"></a>前提条件 開始するには、次が必要です。 * Azure AD サブスクリプション。 サブスクリプションがない場合は、[無料アカウント](https://azure.microsoft.com/free/)を取得できます。 * ScaleX Enterprise でのシングル サインオン (SSO) が有効なサブスクリプション。 ## <a name="scenario-description"></a>シナリオの説明 このチュートリアルでは、テスト環境で Azure AD の SSO を構成してテストします。 * ScaleX Enterprise では、**SP および IDP** Initiated SSO がサポートされます。 ## <a name="add-scalex-enterprise-from-the-gallery"></a>ギャラリーから ScaleX Enterprise を追加する Azure AD への ScaleX Enterprise の統合を構成するには、ギャラリーからマネージド SaaS アプリの一覧に ScaleX Enterprise を追加する必要があります。 1. 職場または学校アカウントか、個人の Microsoft アカウントを使用して、Azure portal にサインインします。 1. 左のナビゲーション ウィンドウで **[Azure Active Directory]** サービスを選択します。 1. **[エンタープライズ アプリケーション]** に移動し、 **[すべてのアプリケーション]** を選択します。 1. 新しいアプリケーションを追加するには、 **[新しいアプリケーション]** を選択します。 1. **[ギャラリーから追加する]** セクションで、検索ボックスに「**ScaleX Enterprise**」と入力します。 1. 結果のパネルから **[ScaleX Enterprise]** を選択し、アプリを追加します。 お使いのテナントにアプリが追加されるのを数秒待機します。 ## <a name="configure-and-test-azure-ad-sso-for-scalex-enterprise"></a>ScaleX Enterprise での Azure AD SSO を構成してテストする **B.Simon** というテスト ユーザーを使用して、ScaleX Enterprise に対する Azure AD SSO を構成してテストします。 SSO を機能させるために、Azure AD ユーザーと ScaleX Enterprise の関連ユーザーとの間にリンク関係を確立する必要があります。 ScaleX Enterprise での Azure AD SSO を構成してテストするには、次の手順を実行します。 1. **[Azure AD SSO の構成](#configure-azure-ad-sso)** - ユーザーがこの機能を使用できるようにします。 1. **[Azure AD のテスト ユーザーの作成](#create-an-azure-ad-test-user)** - B.Simon で Azure AD のシングル サインオンをテストします。 1. **[Azure AD テスト ユーザーの割り当て](#assign-the-azure-ad-test-user)** - B.Simon が Azure AD シングル サインオンを使用できるようにします。 1. **[ScaleX Enterprise の SSO の構成](#configure-scalex-enterprise-sso)** - アプリケーション側でシングル サインオン設定を構成します。 1. **[ScaleX Enterprise のテスト ユーザーの作成](#create-scalex-enterprise-test-user)** - ScaleX Enterprise で B.Simon に対応するユーザーを作成し、Azure AD の B.Simon にリンクさせます。 1. **[SSO のテスト](#test-sso)** - 構成が機能するかどうかを確認します。 ## <a name="configure-azure-ad-sso"></a>Azure AD SSO の構成 これらの手順に従って、Azure portal で Azure AD SSO を有効にします。 1. Azure portal の **ScaleX Enterprise** アプリケーション統合ページで、 **[管理]** セクションを見つけ、 **[シングル サインオン]** を選択します。 1. **[シングル サインオン方式の選択]** ページで、 **[SAML]** を選択します。 1. **[SAML によるシングル サインオンのセットアップ]** ページで、 **[基本的な SAML 構成]** の鉛筆アイコンをクリックして設定を編集します。  1. **[基本的な SAML 構成]** セクションで、アプリケーションを **IDP** 開始モードで構成する場合は、次の手順を実行します。 a. **[識別子]** ボックスに、`https://platform.rescale.com/saml2/<company id>/` の形式で URL を入力します。 b. **[応答 URL]** ボックスに、`https://platform.rescale.com/saml2/<company id>/acs/` のパターンを使用して URL を入力します 1. アプリケーションを **SP** 開始モードで構成する場合は、 **[追加の URL を設定します]** をクリックして次の手順を実行します。 **[サインオン URL]** ボックスに、`https://platform.rescale.com/saml2/<company id>/sso/` という形式で URL を入力します。 > [!NOTE] > これらは実際の値ではありません。 実際の識別子、応答 URL、サインオン URL でこれらの値を更新します。 これらの値を取得するには、[ScaleX Enterprise クライアント サポート チーム](https://about.rescale.com/contactus.html)に問い合わせてください。 Azure portal の **[基本的な SAML 構成]** セクションに示されているパターンを参照することもできます。 1. ScaleX Enterprise アプリケーションでは、特定の形式の SAML アサーションを使用するため、カスタム属性マッピングを SAML トークン属性の構成に追加する必要があります。 次のスクリーンショットは、既定の属性の一覧を示しています。ここで、**emailaddress** は **user.mail** にマップされています。 ScaleX Enterprise アプリケーションでは、**emailaddress** が **user.userprincipalname** にマップされると想定されているため、 **[編集]** アイコンをクリックして属性マッピングを編集し、属性マッピングを変更する必要があります。  1. **[SAML でシングル サインオンをセットアップします]** ページの **[SAML 署名証明書]** セクションで、 **[証明書 (Base64)]** を見つけて、 **[ダウンロード]** を選択し、証明書をダウンロードして、お使いのコンピューターに保存します。  1. **[ScaleX Enterprise のセットアップ]** セクションで、要件に基づいて適切な URL をコピーします。  ### <a name="create-an-azure-ad-test-user"></a>Azure AD のテスト ユーザーの作成 このセクションでは、Azure portal 内で B.Simon というテスト ユーザーを作成します。 1. Azure portal の左側のウィンドウから、 **[Azure Active Directory]** 、 **[ユーザー]** 、 **[すべてのユーザー]** の順に選択します。 1. 画面の上部にある **[新しいユーザー]** を選択します。 1. **[ユーザー]** プロパティで、以下の手順を実行します。 1. **[名前]** フィールドに「`B.Simon`」と入力します。 1. **[ユーザー名]** フィールドに「username@companydomain.extension」と入力します。 たとえば、「 `B.Simon@contoso.com` 」のように入力します。 1. **[パスワードを表示]** チェック ボックスをオンにし、 **[パスワード]** ボックスに表示された値を書き留めます。 1. **Create** をクリックしてください。 ### <a name="assign-the-azure-ad-test-user"></a>Azure AD テスト ユーザーの割り当て このセクションでは、B.Simon に ScaleX Enterprise へのアクセスを許可することで、このユーザーが Azure シングル サインオンを使用できるようにします。 1. Azure portal で **[エンタープライズ アプリケーション]** を選択し、 **[すべてのアプリケーション]** を選択します。 1. アプリケーションの一覧で、 **[ScaleX Enterprise]** を選択します。 1. アプリの概要ページで、 **[管理]** セクションを見つけて、 **[ユーザーとグループ]** を選択します。 1. **[ユーザーの追加]** を選択し、 **[割り当ての追加]** ダイアログで **[ユーザーとグループ]** を選択します。 1. **[ユーザーとグループ]** ダイアログの [ユーザー] の一覧から **[B.Simon]** を選択し、画面の下部にある **[選択]** ボタンをクリックします。 1. SAML アサーション内に任意のロール値が必要な場合、 **[ロールの選択]** ダイアログでユーザーに適したロールを一覧から選択し、画面の下部にある **[選択]** をクリックします。 1. **[割り当ての追加]** ダイアログで、 **[割り当て]** をクリックします。 ## <a name="configure-scalex-enterprise-sso"></a>ScaleX Enterprise の SSO の構成 1. ScaleX Enterprise 内での構成を自動化するには、 **[拡張機能のインストール]** をクリックして **[My Apps Secure Sign-in browser extension]\(My Apps Secure Sign-in ブラウザー拡張機能\)** をインストールする必要があります。  1. ブラウザーに拡張機能を追加した後、 **[ScaleX Enterprise のセットアップ]** をクリックすると、ScaleX Enterprise アプリケーションに誘導されます。 そこから、管理者の資格情報を入力して ScaleX Enterprise にサインインします。 ブラウザー拡張機能によりアプリケーションが自動的に構成され、手順 3 ～ 6 が自動化されます。  1. ScaleX Enterprise を手動でセットアップする場合は、新しい Web ブラウザー ウィンドウを開き、管理者として ScaleX Enterprise 企業サイトにサインインして、次の手順を実行します。 1. 右上隅のメニューを選択し、 **[Contoso Administration (Contoso の管理)]** をクリックします。 > [!NOTE] > Contoso は一例です。 これは、実際の会社名でなければなりません。  1. 上部メニューから **[Integrations]\(統合\)** を選択し、 **[single sign-on]\(シングル サインオン\)** を選択します。 ![ドロップダウン メニューで選択されている [Integrations]\(統合\)、[Single Sign-On]\(シングル サインオン\) を示すスクリーンショット。](./media/scalex-enterprise-tutorial/menu.png) 1. 次のようにフォームの操作を実行します。  a. **[SSO で認証できるユーザーを作成する]** を選択します。 b. **[サービス プロバイダー SAML]** : 値 **urn:oasis:names:tc:SAML:2.0:nameid-format:persistent** を貼り付けます。 c. **[ACS 応答での ID プロバイダーの電子メール フィールドの名前]** : 値 `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` を貼り付けます。 d. **[Identity Provider EntityDescriptor Entity ID]\(ID プロバイダーの EntityDescriptor エンティティ ID\):** Azure portal からコピーした **[Azure AD 識別子]** の値を貼り付けます。 e. **Identity Provider SingleSignOnService URL\(ID プロバイダーの SingleSignOnService URL\):** Azure portal からの **ログイン URL** を貼り付けます。 f. **[Identity Provider public X509 certificate]\(ID プロバイダーのパブリック X509 証明書\):** Azure からダウンロードした X509 証明書をメモ帳で開いて、このボックスに貼り付けます。 証明書の内容の途中に改行が含まれていないことを確認します。 g. 次のチェックボックスをオンにします: **[Enabled]\(有効化\)、[Encrypt NameID]\(暗号 NameID\)、[Sign AuthnRequests]\(AuthnRequests に署名する\)** 。 h. **[Update SSO Settings (SSO 設定を更新する)]** をクリックして設定を保存します。 ### <a name="create-scalex-enterprise-test-user"></a>ScaleX Enterprise のテスト ユーザーの作成 Azure AD ユーザーが ScaleX Enterprise にサインインできるようにするには、ユーザーを ScaleX Enterprise にプロビジョニングする必要があります。 ScaleX Enterprise の場合、プロビジョニングは自動化されたタスクであり、手動の手順は必要ありません。 SSO 資格情報で正しく認証できるすべてのユーザーは、ScaleX 側で自動的にプロビジョニングされます。 ## <a name="test-sso"></a>SSO のテスト このセクションでは、次のオプションを使用して Azure AD のシングル サインオン構成をテストします。 #### <a name="sp-initiated"></a>SP Initiated: * Azure portal で **[このアプリケーションをテストします]** をクリックします。 これにより、ログイン フローを開始できる ScaleX Enterprise のサインオン URL にリダイレクトされます。 * ScaleX Enterprise のサインオン URL に直接移動し、そこからログイン フローを開始します。 #### <a name="idp-initiated"></a>IDP Initiated: * Azure portal で **[このアプリケーションをテストします]** をクリックすると、SSO を設定した ScaleX Enterprise に自動的にサインインされます。 また、Microsoft マイ アプリを使用して、任意のモードでアプリケーションをテストすることもできます。 マイ アプリで [ScaleX Enterprise] タイルをクリックすると、SP モードで構成されている場合は、ログイン フローを開始するためのアプリケーション サインオン ページにリダイレクトされます。IDP モードで構成されている場合は、SSO を設定した ScaleX Enterprise に自動的にサインインされます。 マイ アプリの詳細については、[マイ アプリの概要](../user-help/my-apps-portal-end-user-access.md)に関するページを参照してください。 ## <a name="next-steps"></a>次のステップ ScaleX Enterprise を構成したら、組織の機密データを流出と侵入からリアルタイムで保護するセッション制御を適用できます。 セッション制御は、条件付きアクセスを拡張したものです。 [Microsoft Defender for Cloud Apps でセッション制御を適用する方法をご覧ください](/cloud-app-security/proxy-deployment-aad)。

yue_Hant

f79ded4ee7cbfc54b7762a32612d8561abfebfe6

md

Markdown

README.md

WendelPro/Wendel

489657e2dc5af40012ba86abeddc331adb3b22af

README.md

WendelPro/Wendel

489657e2dc5af40012ba86abeddc331adb3b22af

README.md

WendelPro/Wendel

489657e2dc5af40012ba86abeddc331adb3b22af

# Hello hope you'are all doing good, WendelPro has a great news for you this period hope you will love it and and share it.

eng_Latn

f79e5097ed672a436bdc5915175fd3925206adc1

md

Markdown

README.md

lomatsu/be-the-hero

dac6939286186687d1d4b23149ba4a542a2b3d5b

README.md

lomatsu/be-the-hero

dac6939286186687d1d4b23149ba4a542a2b3d5b

2021-09-02T08:53:11.000Z

2022-02-27T02:33:06.000Z

README.md

lomatsu/be-the-hero

dac6939286186687d1d4b23149ba4a542a2b3d5b

# be-the-hero (Semana Omnistack v11 | Rocketseat) Sistema web e mobile para auxiliar na resolução de problemas locais.

por_Latn

f79e9ae46c634662370f21f325fb4ecee2e0e6d2

md

Markdown

docs/SetupDNS.md

torpedro/pi-local-wifi-server

6973c9ac4784cff84d2bc17300c9e2978eb7500c

2017-12-21T23:38:10.000Z

2017-12-21T23:38:10.000Z

docs/SetupDNS.md

torpedro/pi-local-wifi-server

6973c9ac4784cff84d2bc17300c9e2978eb7500c

2015-06-18T22:25:42.000Z

2015-06-18T22:25:42.000Z

docs/SetupDNS.md

torpedro/pi-local-wifi-server

6973c9ac4784cff84d2bc17300c9e2978eb7500c

Install BIND server ------------------- apt-get install bind9 bind9-doc Register in dhcpd.conf ---------------------- ``` # in subnet definition option domain-name-servers 192.168.42.1; ```

eng_Latn

f79fd0a047a26f4365cd26cf6ac52099e08f65c5

md

Markdown

README.md

kkdesilva/audit-stash

dd9f0ddcae18606f2d1b049c78b8cbc223b194a4

2022-02-09T10:30:38.000Z

2022-02-09T10:30:38.000Z

README.md

kkdesilva/audit-stash

dd9f0ddcae18606f2d1b049c78b8cbc223b194a4

README.md

kkdesilva/audit-stash

dd9f0ddcae18606f2d1b049c78b8cbc223b194a4

# AuditStash Plugin For CakePHP 4.x This plugin is forked from [lorenzo/audit-stash](https://github.com/lorenzo/audit-stash) Although the above plugin is very good for storing change history, it has the following issues or does not have all the features I needed. - Original data is not recorded at the delete event. - This is useful if you add the plugin after some data was added. - Associated table records were not saved properly (In this case I considered two models with ‘hasMany’ relationship) - Currently, in the CakePHP (4.x) ORM when there is a ‘hasMany’ relationship (for example; think about 2 DB tables: items and item_attributes), `EntityTrait::extractOriginal(array $fields)` doesn't return the original value of the associated table’s (item_attributes) original data instead they return the modified values. - Also, there is another bug in CakePHP (4.x) ORM, it marks the associated ('hasMany') entities as dirty, even if there are no changes made to the associated table data. - Unable to records only the changed data columns from the associated tables - Unable to record audit logs when saveMany() is called to save multiple entities. - Unable to set some common configurations for the AuditLog behaviour and/or Table Persister via the app.php - Doesn't record a human-friendly data field from foreign keys - The Create event adds the same data into the 'original' and 'changed' columns - The 'id' (primary key) filed is added to the 'original' and 'changed' data, unless you blacklist it in each model class. (The primary key is recorded as a separate field as well) - Unable to store a user-friendly field value in DB. It is useful to identify the records easily; especially, when the DB stores changed data only. So, I used CakePHP Model::setDisplayField() to retrieve a user-friendly field value. Therefore, I decided to fork from the original project and improve it to support the above missing features. ## Installation You can install this plugin into your CakePHP application using [composer](https://getcomposer.org) and executing the following lines in the root of your application. ``` composer require kdesilva/audit-trail bin/cake plugin load AuditStash ``` If you plan to use ElasticSearch as the storage engine, please refer to [lorenzo/audit-stash](https://github.com/lorenzo/audit-stash) ## Configuration ### Tables / Regular Databases If you want to use a regular database, respectively an engine that can be used via the CakePHP ORM API, then you can use the table persister that ships with this plugin. To do so you need to configure the `AuditStash.persister` option accordingly. In your `config/app.php` file add the following configuration: ```php 'AuditStash' => [ 'persister' => 'AuditStash\Persister\TablePersister' ] ``` The plugin will then by default try to store the logs in a table named `audit_logs`, via a table class with the alias `AuditLogs`, which you could create/overwrite in your application if you need. You can find a migration in the `config/migration` folder of this plugin which you can apply to your database, this will add a table named `audit_logs` with all the default columns. Alternatively you can bake your own migration to create the table. After that you can migrate the corresponding table class. If you use the plugin's default migration, you can create the table and model class using the commands below. ``` bin/cake migrations migrate -p AuditStash -t 20171018185609 bin/cake bake model AuditLogs ``` #### Table Persister Configuration The table persister supports various configuration options, please refer to [its API documentation](/src/Persister/TablePersister.php) for further information. Generally configuration can be applied via its `config()` (or `setConfig()`) method: ```php $this->addBehavior('AuditStash.AuditLog'); $this->behaviors()->get('AuditLog')->persister()->config([ 'extractMetaFields' => [ 'user.name' => 'username' ] ]); ``` Also, you can set some common config via the `app.php`. Currently, the plugin supports 'extractMetaFields' and 'blacklist' ```php ... 'AuditStash' => [ 'persister' => 'AuditStash\Persister\TablePersister', 'extractMetaFields' => [ 'user.username' => 'username', 'user.customer_id' => 'customer_id', ], 'blacklist' => ['customer_id'], ], ``` ## Using AuditStash Enabling the Audit Log in any of your table classes is as simple as adding a behavior in the `initialize()` function: ```php class ArticlesTable extends Table { public function initialize(array $config = []) { $this->setDisplayField('article_name'); ... $this->addBehavior('AuditStash.AuditLog'); } } ``` ### Configuring the Behavior The `AuditLog` behavior can be configured to ignore certain fields of your table, by default it ignores the `id`, `created` and `modified` fields: ```php class ArticlesTable extends Table { public function initialize(array $config = []) { $this->setDisplayField('article_name'); ... $this->addBehavior('AuditStash.AuditLog', [ 'blacklist' => ['created', 'modified', 'another_field_name'] ]); } } ``` If you prefer, you can use a `whitelist` instead. This means that only the fields listed in that array will be tracked by the behavior: ```php class ArticlesTable extends Table { public function initialize(array $config = []) { $this->setDisplayField('article_name'); ... $this->addBehavior('AuditStash.AuditLog', [ 'whitelist' => ['title', 'description', 'author_id'] ]); } } ``` If you need to retrieve human-friendly data fields from related tables (i.e. with foreign keys) you can set `foreignKeys` as below. ```php public function initialize(array $config = []) { $this->setDisplayField('article_name'); ... $this->addBehavior('AuditStash.AuditLog', [ 'blacklist' => ['customer_id', 'product_id'], 'foreignKeys' => [ 'Categories' => 'name', // foreign key Model => human-friendly field name 'ProductStatuses' => 'status', ], 'unsetAssociatedEntityFieldsNotDirtyByFieldName' => [ 'associated_table_name' => 'field_name_in_associated_table' ] ]); } ``` As explained in the project description above, CakePHP (4.x) ORM returns all associated data even if no are changes made to the associated data. Therefore, you need to set `unsetAssociatedEntityFieldsNotDirtyByFieldName` as you can see in the above example if you need to remove unchanged data from the associated entities. ### Storing The Logged In User It is often useful to store the identifier of the user that is triggering the changes in a certain table. For this purpose, `AuditStash` provides the `RequestMetadata` listener class, that is capable of storing the current URL, IP and logged in user. You need to add this listener to your application in the `AppController::beforeFilter()` method: ```php use AuditStash\Meta\RequestMetadata; ... class AppController extends Controller { public function beforeFilter(Event $event) { ... $eventManager = $this->loadModel()->eventManager(); $identity = $this->request->getAttribute('identity'); if ($identity != null) { $eventManager->on( new RequestMetadata($this->request, [ 'username' => $identity['username'], 'customer_id' => $identity['customer_id'], ]) ); } } } ``` The above code assumes that you will trigger the table operations from the controller, using the default Table class for the controller. If you plan to use other Table classes for saving or deleting inside the same controller, it is advised that you attach the listener globally: ```php use AuditStash\Meta\RequestMetadata; use Cake\Event\EventManager; ... class AppController extends Controller { public function beforeFilter(Event $event) { ... $identity = $this->request->getAttribute('identity'); if ($identity != null) { EventManager::instance()->on( new RequestMetadata($this->request, [ 'username' => $identity['username'], 'customer_id' => $identity['customer_id'], ]) ); } } } ``` ### Storing Extra Information In Logs `AuditStash` is also capable of storing arbitrary data for each of the logged events. You can use the `ApplicationMetadata` listener or create your own. If you choose to use `ApplicationMetadata`, your logs will contain the `app_name` key stored and any extra information your may have provided. You can configure this listener anywhere in your application, such as the `bootstrap.php` file or, again, directly in your AppController. ```php use AuditStash\Meta\ApplicationMetadata; use Cake\Event\EventManager; EventManager::instance()->on(new ApplicationMetadata('my_blog_app', [ 'server' => $theServerID, 'extra' => $somExtraInformation, 'moon_phase' => $currentMoonPhase ])); ``` Implementing your own metadata listeners is as simple as attaching the listener to the `AuditStash.beforeLog` event. For example: ```php EventManager::instance()->on('AuditStash.beforeLog', function ($event, array $logs) { foreach ($logs as $log) { $log->setMetaInfo($log->getMetaInfo() + ['extra' => 'This is extra data to be stored']); } }); ``` ### Implementing Your Own Persister Strategies There are valid reasons for wanting to use a different persist engine for your audit logs. Luckily, this plugin allows you to implement your own storage engines. It is as simple as implementing the `PersisterInterface` interface: ```php use AuditStash\PersisterInterface; class MyPersister implements PersisterInterface { public function logEvents(array $auditLogs) { foreach ($auditLogs as $log) { $eventType = $log->getEventType(); $data = [ 'timestamp' => $log->getTimestamp(), 'transaction' => $log->getTransactionId(), 'type' => $log->getEventType(), 'primary_key' => $log->getId(), 'display_value' => $event->getDisplayValue(), 'source' => $log->getSourceName(), 'parent_source' => $log->getParentSourceName(), 'original' => json_encode($log->getOriginal()), 'changed' => $eventType === 'delete' ? null : json_encode($log->getChanged()), 'meta' => json_encode($log->getMetaInfo()) ]; $storage = new MyStorage(); $storage->save($data); } } } ``` Finally, you need to configure `AuditStash` to use your new persister. In the `config/app.php` file add the following lines: ```php 'AuditStash' => [ 'persister' => 'App\Namespace\For\Your\Persister' ] ``` or if you are using as standalone via ```php \Cake\Core\Configure::write('AuditStash.persister', 'App\Namespace\For\Your\DatabasePersister'); ``` The configuration contains the fully namespaced class name of your persister. ### Working With Transactional Queries Occasionally, you may want to wrap a number of database changes in a transaction, so that it can be rolled back if one part of the process fails. In order to create audit logs during a transaction, some additional setup is required. First create the file `src/Model/Audit/AuditTrail.php` with the following: ```php <?php namespace App\Model\Audit; use Cake\Utility\Text; use SplObjectStorage; class AuditTrail { protected $_auditQueue; protected $_auditTransaction; public function __construct() { $this->_auditQueue = new SplObjectStorage; $this->_auditTransaction = Text::uuid(); } public function toSaveOptions() { return [ '_auditQueue' => $this->_auditQueue, '_auditTransaction' => $this->_auditTransaction ]; } } ``` Anywhere you wish to use `Connection::transactional()`, you will need to first include the following at the top of the file: ```php use App\Model\Audit\AuditTrail; use Cake\Event\Event; ``` Your transaction should then look similar to this example of a BookmarksController: ```php $trail = new AuditTrail(); $success = $this->Bookmarks->connection()->transactional(function () use ($trail) { $bookmark = $this->Bookmarks->newEntity(); $bookmark1->save($data1, $trail->toSaveOptions()); $bookmark2 = $this->Bookmarks->newEntity(); $bookmark2->save($data2, $trail->toSaveOptions()); ... $bookmarkN = $this->Bookmarks->newEntity(); $bookmarkN->save($dataN, $trail->toSaveOptions()); return true; }); if ($success) { $event = new Event('Model.afterCommit', $this->Bookmarks); $table->behaviors()->get('AuditLog')->afterCommit($event, $result, $auditTrail->toSaveOptions()); } ``` This will save all audit info for your objects, as well as audits for any associated data. Please note, `$result` must be an instance of an Object. Do not change the text "Model.afterCommit". ### Saving Multiple Entities Create the file `src/Model/Audit/AuditTrail.php` as shown in the above section ```php ... $auditTrail = new AuditTrail(); if ($this->Bookmarks->saveMany($entities, $auditTrail->toSaveOptions())) { ... } ```

eng_Latn

f79fe0562f080dbddd3a73fe156488bcd9467d72

md

Markdown

nunaserver/README.md

UAVCAN/nunaweb

3dc59d5385716a2ad8581807a80d52489ffae8e8

2021-02-10T22:56:35.000Z

2021-09-11T12:43:27.000Z

nunaserver/README.md

UAVCAN/nunaweb

3dc59d5385716a2ad8581807a80d52489ffae8e8

2021-02-03T20:01:19.000Z

2021-10-05T10:24:08.000Z

nunaserver/README.md

bbworld1/nunaweb

3dc59d5385716a2ad8581807a80d52489ffae8e8

2021-02-20T08:29:08.000Z

2021-02-20T08:29:08.000Z

# Nunaserver Nunaserver is the backend for the Nunaweb application. It is responsible for handling uploads from the frontend, generating the output code, then returning a zipped output to the user. It uses Flask (Python 3.7+) and Celery (Redis backend) to handle jobs asynchronously. A static file server of some kind is needed to handle serving outputted zip archives. ## Setting up the Server Setting up nunaserver is slightly complicated due to the several processes it needs to run. A docker+docker-compose development and production setup is in the works to simplify this process. Required tools for the recommended setup process: - Python 3.7+ (and pip) 1. install requirements with `pip3 install -r requirements.txt` 1a. install dev requirements with `pip3 install -r requirements-dev.txt` 2. Run the flask dev server with `python3 -m nunaserver` 3. Run the Celery worker with `celery -A nunaserver.generator worker --loglevel=info` 4. Run a basic static file server with `cd static && python3 -m http.server` This is a dev setup, not meant to be used for production. ## Deploying Deploying the server consists of 3 steps: 1. Changing settings 2. Deploying Flask 3. Deploying Celery 4. Deploying a static file server (Note: Obviously, install dependencies before following these steps) Change the settings in `nunaserver/settings.py` to match your planned production environment. Alternatively, you can set environment variables. Flask can be deployed with any regular WSGI server. For example, Gunicorn: `gunicorn --bind 0.0.0.0:5000 nunaserver.wsgi:app` will run a production WSGI server on port 5000. You can also configure nginx or most other popular web servers to run nunaserver as a WSGI app. The Celery worker can be started in the same way as in the development process. Nunaserver builds and outputs zip archives of generated code in the configured output directory (`static/` by default). A static file server can be configured using your web server of choice.

eng_Latn

f7a007d4fcad01fa3996aadf88ba31041e700c36

md

Markdown

README.md

Dercharles/hodgepodge

9039e87425d7da39d931424b8e036f4ef4e1ecb3

README.md

Dercharles/hodgepodge

9039e87425d7da39d931424b8e036f4ef4e1ecb3

README.md

Dercharles/hodgepodge

9039e87425d7da39d931424b8e036f4ef4e1ecb3

# hodgepodge hodgepodge（大杂烩）这里是一个Gradle项目的初始版本，其余分支均基于本分支开发 万物归于原始初开时 本项目基础继承了如下组件 1. lombok 支持lombok组件[官网地址](https://projectlombok.org/) 2. spring-boot-devtools springBoot开发工具包 3. spring-boot-starter-web springBoot基础web组件 4. spring-boot-configuration-processor springBoot自定义注解支持 ### xiaodan（小单） 致力于打造一个，信息广袤的免费农村货运平台，让互联网技术普惠所有人 ### design-patterns（设计模式的学习-复习） [查看对应文章可点击前往](https://blog.csdn.net/Charles_s/article/details/109632938) 积累技术要点，从最基础的开始，一步一步攀登技术珠峰,作为技术人需要的是沉淀 <br><br> --- > 人生有长有短，有高有低。<br> > 楚王虽雄，难免乌江自刎。<br> > 汉王虽若，却有万里江山。<br> > 满腹经纶，白发不第，<br>才疏学浅，少年登科。<br> > 有先贫而后富，有先富而后贫。<br> > 蛟龙未遇，潜身与鱼虾之间。<br>君子失势拱手与小人之下<br> > 天不得时 日月无光，地不得时，草木不长<br> > 水不得时 风浪不止，人不得时，利运不通<br> > 盖人生在世，富贵不能移，贫贱不能欺，此乃天理循环，终而负时者也。

yue_Hant

f7a057fd2abac92d689bd5cfed0d9e495694e91e

md

Markdown

README.md

jtarte/ics-remote-manager

35167ddeeebaf7889ef5ac560e9d061a3f154cf7

2020-03-10T12:14:27.000Z

2020-03-10T12:14:27.000Z

README.md

jtarte/ics-remote-manager

35167ddeeebaf7889ef5ac560e9d061a3f154cf7

README.md

jtarte/ics-remote-manager

35167ddeeebaf7889ef5ac560e9d061a3f154cf7

**A sample application that shows how to interact remotely with IBM Bluemix Container Service via API** ## Summary This is a sample application that shows how to use the API to interact with IBM Bluemix Container Service The IBM Bluemix Container Service API is available at: http://ccsapi-doc.mybluemix.net ## Deployment The application could be run locally, using a local instance of nodejs. $ node app.js The application could also be deployed on Bluemix by using the [manifest](./manifest.yml) file $ cf push Be careful with the route used for the deployment, the route could be already used. May be you have to change it for your deployment. ## Contributing Jérôme Tarte, IBM Cloud Advisor, jerome.tarte@fr.ibm.com ## License Copyright IBM Corp. 2017 This project is licensed under Apache license - see the [license.md](./license.md) file

eng_Latn

f7a1426a643e138a781729a8cb318ddc8e8296a5

md

Markdown

README.md

ahkhystrix/rebrain-devops-task-checkout

7cbf2a8f53dd6b96b446dadc9a6383897089f9a7

README.md

ahkhystrix/rebrain-devops-task-checkout

7cbf2a8f53dd6b96b446dadc9a6383897089f9a7

README.md

ahkhystrix/rebrain-devops-task-checkout

7cbf2a8f53dd6b96b446dadc9a6383897089f9a7

# FFID - Flat Files Import to Database The program is designed to import data from text files into a database. During the import process, key-value pairs are automatically detected, tabs and spaces are used as delimiters. ## Getting Started ### Prerequisites Install Git and Python. Example for CentOS and RHEL-based: ``` sudo yum install git sudo yum install python ``` Example for Ubuntu and Debian-based: ``` sudo apt-get install git sudo apt-get install python ``` ### Installing Make a repository clone: ``` git clone https://github.com/ahkhystrix/rebrain-devops-task-checkout.git ``` ### Running Go to the installed program directory: ``` cd rebrain-devops-task-checkout ``` Run the script by specifying the path to the directory where the text files are stored: ``` python ffid.py /var/textfiles ``` ## Authors * **Alexey Kuznetsov** - [ahkhystrix](https://github.com/ahkhystrix) ## License This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details

eng_Latn

f7a237a405b95d45b28e0fcf18ce2618c1a3172a

md

Markdown

pages/how-we-protect-your-data/system-of-records-notices.md

frtib/tsp-redesign

7d733182a4fa0900799f0f10bb096259113e7110

2018-07-06T20:46:03.000Z

2021-02-04T13:38:42.000Z

pages/how-we-protect-your-data/system-of-records-notices.md

frtib/tsp-redesign

7d733182a4fa0900799f0f10bb096259113e7110

2018-07-25T21:16:13.000Z

2021-07-29T00:26:11.000Z

pages/how-we-protect-your-data/system-of-records-notices.md

frtib/tsp-redesign

7d733182a4fa0900799f0f10bb096259113e7110

2019-02-07T22:23:01.000Z

2021-03-30T21:14:53.000Z

--- layout: page title: System of Records Notices (SORNs) sidenav: privacy styles: scripts: permalink: /how-we-protect-your-data/system-of-records-notices/ --- # System of Records Notices (SORNs) The Privacy Act of 1974 requires all federal agencies to publish a formal notice to the public in the Federal Register that identifies the purposes for which personally identifiable information (PII) is collected; how the PII is used by the Agency; how the Agency shares PII externally; and, most importantly, how individuals can access and correct the information a federal government agency maintains on the subject individual. These notices are called System of Records Notices (SORNs). FRTIB is required to publish a SORN anytime it creates, substantially modifies, or retires a system of records. A system of records is a collection of records under the control of a federal agency from which information about a specific individual can be retrieved or accessed by a unique personal identifier (e.g., name or account number). ## FRTIB has the following systems of records: <ul class="usa-accordion-bordered"> <!-- FRTIB-1 --> <li id="frtib-1"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a1"> FRTIB-1 | Thrift Savings Plan Records </button> <div id="a1" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 53370]({{ site.baseurl }}/exit/?idx=213) **SYSTEM NAME AND NUMBER:** FRTIB-1, Thrift Savings Plan Records. **SECURITY CLASSIFICATION:** This system contains unclassified information. **SYSTEM LOCATION:** These records are located at the office of the entity engaged by the Agency to perform record keeping services for the Thrift Savings Plan (TSP). The current address for this record keeper is listed at https://www.tsp.gov. **SYSTEM MANAGER(S):** Director, Office of Participant Services, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000 Washington, DC 20002, (202) 942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; Thrift Savings Plan (TSP) Enhancement Act of 2009, Pub L. 111-31. **PURPOSE(S) OF THE SYSTEM:** The purpose of this system of records is to ensure the integrity of the Plan, to record activity concerning the TSP account of each Plan participant, to communicate with the participant, spouse, former spouse, and beneficiary concerning the account, and to make certain that he or she receives a correct payment from the Plan. Information contained in the system will also be used to comply with the reporting requirements of the TSP Enhancement Act of 2009 and to develop outreach and educational initiatives for participants and beneficiaries. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** All participants (which term includes former participants, i.e., participants whose accounts have been closed), as well as spouses, former spouses, and beneficiaries of TSP participants. Participants in the TSP consist of present and former Members of Congress and Federal employees covered by the Federal Employees' Retirement System Act of 1986, (FERSA) as amended, 5 U.S.C. chapter 84; all present and former Members of Congress and Federal employees covered by the Civil Service Retirement System who elect to contribute to the TSP; Supreme Court Justices, Federal judges, and magistrates who elect to contribute; certain union officials, those individuals described in 5 CFR part 1620, and any other individual for whom an account has been established. **CATEGORIES OF RECORDS IN THE SYSTEM:** These records contain the following kinds of information: Records of TSP account activity, including account balances, employee contributions, agency automatic (one percent) and agency matching contributions, earnings, interfund transfers, contribution allocation elections, investment status by fund, loan and withdrawal information, employment status, retirement code and whether employee is vested, error correction information, participant's date of birth, email address, phone number, and designated beneficiary; records of spousal waivers and consents; powers of attorney and conservatorship and guardianship orders; participant's name, current or former employing agency, and servicing payroll and personnel office; records of Social Security number, TSP account number, TSP PIN, and home address for participants, spouses, former spouses, and beneficiaries and potential beneficiaries; demographic information (e.g., gender, education information, ethnicity, race, etc.); demographic information on uniformed services participants (e.g., grade, service branch, rank, months in rank, occupation information); death certificates; records of bankruptcy actions; information regarding domestic relations court orders to divide the account; child support, child abuse, and alimony orders; information on payments to the participant's spouse, former spouse, or children and their attorneys; information on notices sent to participants, spouses, former spouses, and beneficiaries; and general correspondence. Documents used to verify identity including: birth certificate, U.S. passport, driver's license or state-issued ID, or other government-issued ID that can be used to verify identity. **RECORD SOURCE CATEGORIES:** The information in this system is obtained from the following sources: (a) The individual to whom the information pertains; (b) Agency payroll and personnel records; (c) Court orders; or (d) Spouses, former spouses, other family members, beneficiaries, legal guardians, and personal representatives (executors, administrators). **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, 5 U.S.C. 552a(b) and: 1. Routine Use&#8212;Tax Enforcement Agencies: To disclose financial data and addresses to Federal, state, and local governmental tax enforcement agencies so that they may enforce applicable tax laws. 2. Routine Use&#8212;Designated Annuity Vendor: To disclose to the designated annuity vendor in order to provide TSP participants who have left Federal service with an annuity. 3. Routine Use&#8212;Other Retirement Plans: To disclose to sponsors of eligible retirement plans for purposes of transferring the funds in the participant's account to an Individual Retirement Arrangement or into another eligible retirement plan. 4. Routine Use&#8212;Spousal Rights: To disclose to current and former spouses and their attorneys in order to protect spousal rights under FERSA and to receive benefits to which they may be entitled. 5. Routine Use&#8212;Death Benefits, Beneficiaries: When a participant to whom a record pertains dies, to disclose the following types of information to any potential beneficiary: Information in the participant's record which could have been properly disclosed to the participant when living (unless doing so would constitute a clearly unwarranted invasion of privacy) and the name and relationship of any other person who claims the benefits or who is entitled to share the benefits payable. 6. Routine Use&#8212;Death Benefits, Estate Administration: When a participant to whom a record pertains dies, to disclose the following types of information to anyone handling the participant's estate: Information in the participant's record which could have been properly disclosed to the participant when living (unless doing so would constitute a clearly unwarranted invasion of privacy), the name and the relationship of any person who claims the benefits or who is entitled to share the benefits payable, and information necessary for the estate's administration (for example, post-death tax reporting). 7. Routine Use&#8212;Beneficiaries, Incompetent or Legal Disability: To disclose information to any person who is named by the participant, spouse, former spouse, or beneficiary of the participant in a power of attorney and to any person who is responsible for the care of the participant or the spouse, former spouse, or beneficiary of the participant to whom a record pertains, and who is found by a court to be incompetent or under other legal disability, information necessary to manage the participant's account and to ensure payment of benefits to which the participant, spouse, former spouse or beneficiary of the participant is entitled. 8. Routine Use&#8212;Congressional Inquiries: To disclose information to a congressional office from the record of a participant or of the spouse, former spouse, or beneficiary of a participant in order for that office to respond to a communication from that person. 9. Routine Use&#8212;Agency Payroll or Personnel Offices: To disclose to agency payroll or personnel offices in order to calculate benefit projections for individual participants, to calculate error corrections, to reconcile payroll records, and otherwise to ensure the effective operation of the Thrift Savings Plan. 10. Routine Use&#8212;Department of Treasury, Payments: To disclose to the Department of the Treasury information necessary to issue checks from accounts of participants in accordance with withdrawal or loan procedures or to make a payment to a spouse, former spouse, child, or his or her attorney, or to a beneficiary. 11. Routine Use&#8212;Audit: To disclose to the Department of Labor and to private sector audit firms so that they may perform audits as provided for in FERSA. 12. Routine Use&#8212;Parent Locator Service: To disclose to the Parent Locator Service of the Department of Health and Human Services, upon its request, the address of a participant, spouse, former spouse, or beneficiary of the participant for the purpose of enforcing child support obligations against that individual. 13. Routine Use&#8212;Investigations, Third Parties: To disclose pertinent information to the appropriate Federal, foreign, state, local, or tribal agency, or to other public authority responsible for investigating, prosecuting, enforcing, or implementing a statute, rule, regulation, or order, upon its request, when presented with an indication that the information is relevant to any enforcement, regulatory, investigative, or prosecutorial responsibility of that agency or authority. 14. Routine Use&#8212;Private Relief Legislation: To disclose information to the Office of Management and Budget at any stage of the legislative coordination and clearance process in connection with private relief legislation as set forth in OMB Circular No. A-19. 15. Routine Use&#8212;Participant and Third Parties, Health or Safety: If there is a reasonable and credible threat to an individual’s health or safety, to disclose to a state, local, or Federal agency, in response to its request, the address of a participant, spouse, former spouse, or beneficiary of the participant and any other information the agency needs to contact that individual concerning the possible threat to his or her health or safety. 16. Routine Use&#8212;Litigation, Department of Justice: To disclose information to the Department of Justice, where: 1. The Board or any component of it, or 2. Any employee of the Board in his or her official capacity, or 3. Any employee of the Board in his or her individual capacity, where the Department of Justice has agreed to represent the employee; or 4. The United States (where the Board determines that litigation is likely to affect the agency or any of its components) is a party to litigation or has an interest in such litigation, and the Board determines that use of such records is relevant and necessary to the litigation. However, in each such case, the Board must determine that disclosure of the records to the Department of Justice is a use of the information contained in the records which is compatible with the purpose for which the records were collected. 17. Routine Use&#8212;Litigation, Third Parties: In response to a court subpoena, or to appropriate parties engaged in litigation or preparing for possible litigation. Examples include disclosure to potential witnesses for the purpose of securing their testimony to courts, magistrates, or administrative tribunals, to parties and their attorneys in connection with litigation or settlement of disputes, or to individuals seeking information through established discovery procedures in connection with civil, criminal, or regulatory proceedings. 18. Routine Use&#8212;Contractors and Third Parties: To disclose to contractors and their employees who have been engaged to assist the Board in performing a contract service or agreement, or who have been engaged to perform other activity related to this system of records and who need access to the records in order to perform the activity. Recipients of TSP records are required to comply with the requirements of the Privacy Act. 19. Routine Use&#8212;Agency Personnel/Payroll Offices or Casualty Assistance Officers: To disclose to personnel from agency personnel/payroll offices or to casualty assistance officers when necessary to assist a beneficiary or potential beneficiary. 20. Routine Use&#8212;Consumer Reporting Agencies: To disclose to a consumer reporting agency when the Board is trying to collect a debt owed to the Board under the provisions of 5 U.S.C. 3711. 21. Routine Use&#8212;Commercial Loan Applications, Quality Control: To disclose to quality control companies when such companies are verifying documents submitted to lenders in connection with participants' commercial loan applications. 22. Routine Use&#8212;Federal Agencies, Analysis: To disclose to an official of another Federal agency information needed in the performance of official duties related to reconciling or reconstructing data files, compiling descriptive statistics, and making analytical studies in support of the function for which the records were collected and maintained. 23. Routine Use&#8212;Breach Mitigation and Notification: A record from this system may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 24. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** These records are maintained on electronic or magnetic media, on microfilm, or in folders. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** These records are retrieved by Social Security number, TSP account number, and other personal identifiers of the individual to whom they pertain. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** TSP documents are retained for 99 years. Manual records are disposed of by compacting and burning; data on electronic or magnetic media are obliterated by destruction or reuse, or are returned to the employing agency. Call recording records from the Agency’s contact center are retained in accordance with NARA General Records Schedule 6.5, Public Customer Services Records, DAA-GRS-2017-0002-0001. **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** Hard copy records are kept in metal file cabinets in a secure facility, with access limited to those whose official duties require access. Personnel are screened to prevent unauthorized disclosure. Security mechanisms for automatic data processing prevent unauthorized access to the electronic or magnetic media. **RECORD ACCESS PROCEDURES:** Individuals who want notice of whether this system of records contains information pertaining to them and to obtain access to their records may contact the TSP Service Office or their employing agency, as follows: 1. Participants who are current Federal employees may call or write their employing agency for personnel or payroll records regarding the agency’s and the participant's contributions and adjustments to contributions. A request to the employing agency must be made in accordance with that agency's Privacy Act regulations or that agency's procedures. For other information regarding their TSP accounts, participants who are Federal employees may call or write the TSP Service Office. 2. Participants who have separated from Federal employment and spouses, former spouses, and beneficiaries of participants may call or write the TSP Service Office. {: .alpha} Individuals calling or writing the TSP Service Office must furnish the following information for their records to be located and identified: 1. Name, including all former names; 2. TSP Account Number or Social Security number; and 3. Other information, if necessary. For example, a participant may need to provide the name and address of the agency, department, or office in which he or she is currently or was formerly employed in the Federal service. A spouse, former spouse, or beneficiary of a participant may need to provide information regarding his or her communications with the TSP Service Office or the Board. {: .alpha} Participants may also inquire whether this system contains records about them and access certain records through the account access section of the TSP Web site and the ThriftLine (the TSP's automated telephone system). The TSP Web site is located at www.tsp.gov. To use the TSP ThriftLine, the participant must have a touch-tone telephone and call the following number 1-877-968-3778. Hearing-impaired participants should dial 1-877-847-4385. The following information is available on the TSP Web site and the ThriftLine: Account balance; available loan amount; the status of a monthly withdrawal payment; the current status of a loan or withdrawal application; and an interfund transfer request. **CONTESTING RECORD PROCEDURES:** Individuals who want to amend TSP records about themselves must submit a detailed written explanation as to why information regarding them is inaccurate or incorrect, as follows: 1. Participants who are current Federal employees must write their employing agency to request amendment of personnel records regarding employment status, retirement coverage, vesting code, and TSP service computation date, or payroll records regarding the agency's and the participant's contributions and adjustments to contributions. A request to the employing agency must be made in accordance with that agency's Privacy Act regulations or that agency's procedures. For other information regarding their TSP accounts, participants who are Federal employees must submit a request to the TSP Service Office. 2. Participants who have separated from Federal employment and spouses, former spouses, and beneficiaries of participants must submit a request to the TSP Service Office. 3. Individuals must provide their Social Security number and name, and they may also need to provide other information for their records to be located and identified. {: .alpha} The employing agency or the TSP Service Office will follow the procedures set forth in 5 CFR part 1605, Error Correction Regulations, in responding to requests to correct contribution errors. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None **HISTORY:** 52 FR 12065 (Apr. 14, 1987); 55 FR 18949 (May 7, 1990); 59 FR 26496 (May 20, 1994); 64 FR 50092 (Sept. 15, 1999); 64 FR 67917 (Dec. 3, 1999); 74 FR 3043 (Jan. 16, 2009); 77 FR 11534 (Feb. 27, 2012); 77 FR 20022 (Apr. 3, 2012); 79 FR 21246 (Apr. 15, 2014). </div> </li> <!-- FRTIB-2 --> <li id="frtib-2"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a2"> FRTIB-2 | Personnel Security Investigation Files </button> <div id="a2" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43655 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170) **SYSTEM NAME AND NUMBER:** FRTIB-2, Personnel Security Investigation Files. **SECURITY CLASSIFICATION:** Most personnel identity verification records are not classified. However, in some cases, records of certain individuals, or portions of some records may be classified in the interest of national security. **SYSTEM LOCATION:** Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be kept at an additional location as backup for Business Continuity purposes. For background investigations adjudicated by the Office of Personnel Management (OPM), OPM may retain copies of those files pursuant to OPM/Central-9, Personnel Investigations Records. **SYSTEM MANAGER(S):** Chief, Business Continuity and Security Services Division, 77 K Street NE, Suite 1000, Washington, DC 20002, (202) 942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 3301; 44 U.S.C. 3101; E.O. 10450; E.O. 13488; 5 CFR 731 and 736; 61 FR 6428; and Homeland Security Presidential Directive 12. **PURPOSE(S) OF THE SYSTEM:** The records in this system of records are used to document and support decisions regarding clearance for access to sensitive FRTIB information, the ability to receive and the suitability, eligibility, and fitness for service of applicants for federal employment and contract positions, including students, interns, or volunteers to the extent their duties require access to federal facilities, information systems, or applications. The records may also be used to help streamline and make more efficient the investigations and adjudications process generally. The records may also be used to document security violations and supervisory actions taken in response to such violations. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** Individuals who require regular, ongoing access to FRTIB facilities, information technology systems, or sensitive information, including current and former applicants for employment or contracts, federal employees, government contractors, students, interns, volunteers, affiliates, experts, instructors, and consultants to federal programs who undergo a background investigation for the purposes of determining suitability for employment, contractor fitness, credentialing for HSPD-12, and/or access to FRTIB facilities or information technology systems. This system also includes individuals accused of security violations or found in violation of FRTIB’s security policies. **CATEGORIES OF RECORDS IN THE SYSTEM:** Name; former names; date and place of birth; Social Security number; home address; email address(es); phone numbers; employment history; residential history; education and degrees earned; citizenship; passport information; names, date and place of birth, Social Security number, and citizenship information for spouse or cohabitant; the name and marriage information for current and former spouse(s); names of associates and references and their contact information; names, dates and places of birth, citizenship, and address of relatives; names of relatives who work for the federal government; information on foreign contacts and activities; association records; information on loyalty to the United States; criminal history; mental health history; information pertaining to drug use; financial information; fingerprints; information from the Internal Revenue Service pertaining to income tax returns; credit reports; information pertaining to security clearances; other agency reports furnished to FRTIB in connection with the background investigation process; summaries of personal and third party interviews conducted during the background investigation; results of suitability decisions; level of security clearance; date of issuance of security clearance; including,but not limited to forms such as SF-85, SF-85P, SF-86, SF-87, SF-306; FD-258; and other information generated from above, where applicable. Records pertaining to security violations may contain information pertaining to circumstances of the violation; witness statements, investigator’s notes, security violations; agency action taken; requests for appeal; and documentation of agency action taken in response to security violations. **RECORD SOURCE CATEGORIES:** Information is obtained from a variety of sources including the employee, contractor, or applicant via use of the SF-85, SF-85P, SF-86 SF-306, or SF-87, personal interviews with various individuals, including, but not limited to the subject of the investigation, witnesses, present and former employers, references, neighbors, friends, co-workers, business associates, teachers, landlords, family members, or other associates who may have information about the subject of the investigation; investigative records and notices of personnel actions furnished by other federal agencies; records from employers and former employers; public records, such as court filings; publications such as newspapers, magazines, and periodicals; FBI criminal history records and other databases; police departments; probation officials; prison officials financial institutions and credit reports; tax records; medical records and health care providers; and educational institutions. Security violation information is obtained from a variety of sources, such as guard reports, security inspections, witnesses, supervisor’s reports, audit reports. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, 5 U.S.C. 552a(b), and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Clearance Processing: A record from this system of records may be disclosed to an appropriate federal, state, local, tribal, foreign, or international agency, if the information is relevant and necessary to a requesting agency’s decision concerning the hiring or retention of an individual, or issuance of a security clearance, background investigation, license, contract, grant, or other benefit, or if the information is relevant and necessary to a FRTIB decision concerning the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant or other benefit and when disclosure is appropriate to the proper performance of the official duties of the person making the request. 3. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 4. Routine Use&#8212;Contractors, et al.: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 5. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person’s former area of responsibility. 6. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 7. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 8. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 9. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 10. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 11. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 12. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 14. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. 15. Routine Use&#8212;Retention of Employee by Authorized Entity: A record from this system of records may be disclosed to any authorized source or potential source from which information is requested in the course of an investigation concerning the retention of an employee or other personnel action (other than hiring), or the retention of a security clearance, contact, grant, license, or other benefit, to the extent necessary to identify the individual, to inform the source of the nature and purpose of the investigation, or to identify the type of information requested. 16. Routine Use&#8212;Labor Relations: A record from this system of records may be disclosed to OPM, the Merit Systems Protection Board, the Federal Labor Relations Authority, the Office of Special Counsel, or the Equal Employment Opportunity Commission to carry out its respective authorized functions (under 5 U.S.C. 1103, 1204, and 7105 and 42 U.S.C. 2000e-4, in that order). 17. Routine Use&#8212;Private Relief Legislation: A record from this system of records may be disclosed to the Office of Management and Budget when necessary to the review of private relief legislation pursuant to OMB Circular No. A-19. 18. Routine Use&#8212;Retention of Employee by Public Entity: A record from this system of records may be disclosed to a Federal, State, local, foreign, or tribal or other public authority the fact that this system of records contains information relevant to the retention of an employee, the retention of a security clearance, the letting of a contract, or the issuance or retention of a license, grant, or other benefit. The other agency or licensing organization may then make a request supported by the written consent of the individual for the entire record if it so chooses. No disclosure will be made unless the information has been determined to be sufficiently reliable to support a referral to another office within the agency or to another Federal agency for criminal, civil, administrative personnel or regulatory action. 19. Routine Use&#8212;News Media, Public Interest: A record from this system of records may be disclosed to the news media or the general public, factual information the disclosure of which would be in the public interest and which would not constitute an unwarranted invasion of personal privacy, consistent with Freedom of Information Act standards. 20. Routine Use&#8212;National Security: A record from this system of records may be disclosed to a Federal, State, or local agency, or other appropriate entities or individuals, or through established liaison channels to selected foreign governments, in order to enable an intelligence agency to carry out its responsibilities under the National Security Act of 1947 as amended, the CIA Act of 1949 as amended, Executive Order 12333 or any successor order, applicable national security directives, or classified implementing procedures approved by the Attorney General and promulgated pursuant to such statutes, orders or directives 21. Routine Use&#8212;Breach Mitigation and Notification: A record from this system of records may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 22. Routine Use&#8212;Response to Breach of Other Records: A record from this system of records may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained in paper and electronic form, including on computer databases, all of which are stored in a secure location. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Background investigation files are retrieved by any one or more of the following identifiers: Name; Social Security number; or other unique identifier of the individual about whom they are maintained. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** These records are retained and disposed of in accordance with General Records Schedule 18, item 22a, approved by the National Archives and Records Administration (NARA). The records are disposed in accordance with FRTIB disposal policies which call for burning or shredding or deleting from the Agency’s electronic record keeping systems. Records are destroyed upon notification of death or not later than five years after separation or transfer of employee to another agency or department, whichever is applicable. **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB’s security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in locked file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks and protected by assigning usernames to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves should submit a written request to the appropriate entity below, and include the following information: > 1. Full name; > 2. Any available information regarding the type of record involved; > 3. The address to which the record information should be sent; and > 4. You must sign your request > {:.alpha} 1. For records maintained by FRTIB, submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Washington, DC 20002; or 2. For records maintained by the Office of Personnel Management, submit a written request to the FOI/PA, Office of Personnel Management, Federal Investigative Services, P.O. Box 618, 1137 Branchton Road, Boyers, PA 16018-0618. Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB’s Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** Pursuant to 5 U.S.C. 552a(k)(2), records in this system of records are exempt from the requirements of subsections (c)(3); (d); (e)(1); (e)(4)(G), (H), (I); and (f) of 5 U.S.C. 552a. provided, however, that if any individual is denied any right, privilege, or benefit that he or she would otherwise be entitled to by federal law, or for which he or she would otherwise be eligible, as a result of the maintenance of these records, such material shall be provided to the individual, except to the extent that the disclosure of the material would reveal the identity of a source who furnished information to the Government with an express promise that the identity of the source would be held in confidence. Pursuant to 5 U.S.C. 552a(k)(5), records in this system of records are exempt from the requirements of subsections (c)(3); (d); (e)(1); (e)(4)(G), (H), (I); and (f) of 5 U.S.C. 552a, but only to the extent that the disclosure of such material would reveal the identity of a source who furnished information to the Government under an express promise that the identity of the source would be held in confidence. **HISTORY:** 55 FR 18949 (May 7, 1990); 62 FR 59708 (Nov. 4, 1997); 73 FR 50016 (Aug. 25, 2008); 77 FR 11534 (Feb. 27, 2012); 80 FR 43428 (July 22, 2015); 85 FR 43654 (July 17, 2020). </div> </li> <!-- FRTIB-3 --> <li id="frtib-3"> <button class="usa-accordion-button" disabled aria-expanded="false" aria-controls="a3"> FRTIB-3 | Retired </button> <div id="a3" class="usa-accordion-content" markdown="1"></div> </li> <!-- FRTIB-4 --> <li id="frtib-4"> <button class="usa-accordion-button" disabled aria-expanded="false" aria-controls="a4"> FRTIB-4 | Retired </button> <div id="a4" class="usa-accordion-content" markdown="1"></div> </li> <!-- FRTIB-5 --> <li id="frtib-5"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a5"> FRTIB-5 | Employee Payroll, Leave, and Attendance Records </button> <div id="a5" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43658 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170) **SYSTEM NAME AND NUMBER:** FRTIB-5, Employee Payroll, Leave, and Attendance Records. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records are located at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be maintained at additional locations for Business Continuity purposes. **SYSTEM MANAGER:** For payroll records, FRTIB’s Human Resources Officer, 77 KStreet NE, Suite 1000, Washington, DC 20002, (202) 942-1600. For leave and attendancerecords, FRTIB’s Administrative Officer, 77 K Street NE, Suite 1000, Washington, DC 20002, (202) 942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; and 44 U.S.C. 3101. **PURPOSE(S) OF THE SYSTEM:** This system of records is maintained to perform agency functions involving employee leave, attendance, and payments, including determinations relating to the amounts to be paid to employees, the distribution of pay according to employee directions (for allotments, to financial institutions, and for other authorized purposes), and for tax withholdings and other authorized deductions. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** Current and former FRTIB employees, including Special Government Employees. **CATEGORIES OF RECORDS IN THE SYSTEM:** This system of records includes personnel information including, names, addresses, Social Security numbers, employee numbers, gender, race or national origin, and disability data; duty location; position data; awards and bonus information; employment verification information; notifications of personnel actions; and military and veterans data. This system of records also includes payroll information, including: Marital status and number of dependents; child support enforcement court orders; information about taxes and other deductions; debts owed to the FRTIB and garnishment information; salary data; retirement data; Thrift Savings Plan contribution and loan amount; and direct deposit information, including financial institution. This system of records also includes time and attendance records including, the number and type of hours worked; overtime information, including compensatory or credit time earned and used; compensatory travel earned; investigative case title and tracking number (used to track time worked associated with a specific case); Fair Labor Standards Act (FLSA) compensation; leave requests, balances, and credits; leave charge codes; military leave; and medical records as they pertain to employee medical leave. **RECORD SOURCE CATEGORIES:** Subject individuals; subject individuals’ supervisor(s); subject individuals’ timekeeper(s); and the Office of Personnel Management. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, 5 U.S.C. 552a(b), and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Clearance Processing: A record from this system of records may be disclosed to an appropriate federal, state, local, tribal, foreign, or international agency, if the information is relevant and necessary to a requesting agency’s decision concerning the hiring or retention of an individual, or issuance of a security clearance, background investigation, license, contract, grant, or other benefit, or if the information is relevant and necessary to a FRTIB decision concerning the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant or other benefit and when disclosure is appropriate to the proper performance of the official duties of the person making the request. 3. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 4. Routine Use&#8212;Contractors, et al.: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 5. Routine Use&#8212;Debt Collection: A record from this system of records may be disclosed to the Department of Justice, the Department of Treasury, or to a consumer reporting agency for collection action on any delinquent debt, pursuant to 5 U.S.C. 552a(b)(12). 6. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person’s former area of responsibility. 7. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 8. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 9. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 10. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 11. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 12. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 13. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 14. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 15. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. 16. Routine Use&#8212;Disclosure for Purpose of Payment to Employees: A record from this system may be disclosed to the United States Department of the Interior, the United States Department of Labor, and the United States Department of the Treasury to effect payments to employees. 17. Routine Use&#8212;Offset of Salary: Payments owed to FRTIB through current and former employees may be shared with the Department of the Interior for the purposes of offsetting the employee’s salary. Payments owed to FRTIB through current and former employees who become delinquent in repaying the necessary funds may be shared with the Department of Treasury for the purpose of offsetting the employee’s salary. 18. Routine Use&#8212;Breach Mitigation and Notification: A record from this system may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 19. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained in paper and electronic form, including on computer databases, all of which are stored in a secure location. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Records are retrieved by name; or Social Security number. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** Records are maintained in accordance with the General Records Schedules issued by the National Archives and Records Administration (NARA) or an FRTIB records disposition schedule. **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB’s security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in locked file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks and protected by assigning usernames to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves should submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Washington, DC 20002, and include the following information: 1. Full name; 2. Any available information regarding the type of record involved; 3. The address to which the record information should be sent; and 4. You must sign your request. {: .alpha} Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB’s Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **HISTORY:** 55 FR 18949 (May 7, 1990); 62 FR 66097 (Dec. 17, 1997); 77 FR 11534 (Feb. 27, 2012); 80 FR 43428 (July 22, 2015); 85 FR 43654 (July 17, 2020). </div> </li> <!-- FRTIB-6 --> <li id="frtib-6"> <button class="usa-accordion-button" disabled aria-expanded="false" aria-controls="a6"> FRTIB-6 | Retired </button> <div id="a6" class="usa-accordion-content" markdown="1"></div> </li> <!-- FRTIB-7 --> <li id="frtib-7"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a7"> FRTIB-7 | Contractor and Consultant Records </button> <div id="a7" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43660 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170) **SYSTEM NAME AND NUMBER:** FRTIB-7, Contractor and Consultant Records **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be kept at an additional location as backup for Business Continuity purposes. **SYSTEM MANAGER(S):** Chief Procurement Officer, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002, (202) 942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; 5 U.S.C. 3301; and 44 U.S.C. 3101. **PURPOSE(S) OF THE SYSTEM:** The purpose of this system of records is to collect and maintain records on FRTIB contractors and consultants. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** Individuals retained by formal agreement, who: (1) Provide consulting services to the Board; (2) act as advisors to the Board, but do not maintain the independence of action necessary to meet the requirements for classification as an independent contractor; and (3) any other individuals who receive payments from FRTIB. **CATEGORIES OF RECORDS IN THE SYSTEM:** Acquisition data for the procurement of goods and services, including, but not limited to: Documents, letters, memorandum of understanding relating to agreements; rates of pay; payment records; vouchers; invoices; selection information; Commercial and Government Entity (CAGE) codes; Dun and Bradstreet Data Universal Numbering System (DUNS) numbers; supplier status; Web site; name; address; taxpayer identification number; Social Security numbers; bank information; invoice data; resumes; SAC forms; and other information relating to the disbursement of funds. This system of records also contains information pertaining to the negotiation; implementation; scope; and performance of work. **RECORD SOURCE CATEGORIES:** Information in this system of records is obtained from the individual to whom it applies or is derived from information supplied by the individual, except information provided by Board staff. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, 5 U.S.C. 552a(b), and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 3. Routine Use&#8212;Contractors, et al.: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 4. Routine Use&#8212;Debt Collection: A record from this system of records may be disclosed to the Department of Justice, the Department of Treasury, or to a consumer reporting agency for collection action on any delinquent debt, pursuant to 5 U.S.C. 552a(b)(12). 5. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person’s former area of responsibility. 6. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 7. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 8. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 9. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 10. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 11. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 12. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 13. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 14. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. 15. Routine Use&#8212;Testing: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign governmental agencies or multilateral governmental organizations where FRTIB is aware of a need to utilize relevant data for purposes of testing new technology and systems designed to enhance security or identify other violations of law. 16. Routine Use&#8212;Payments to Consultants and Vendors: A record from this system of records may be disclosed to the United States Department of the Treasury to effect payments to consultants and vendors, or to verify consultants’ and vendors’ eligibility to receive payments. 17. Routine Use&#8212;Breach Mitigation and Notification: A record from this system may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 18. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained in paper and electronic form, including on computer databases, all of which are stored in a secure location. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Contractor and consultant files are retrieved by any one or more of the following identifiers: Name of the contractor; name of the vendor or contractor; voucher number and date; or other unique identifier about whom they are maintained. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** Routine procurement files are retained for 6 years and 3 months, in accordance with the General Records Schedule 3, item 3. Procurement files involving investments and other information concerning the Thrift Savings Plan are retained for 99 years. **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB’s security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in locked file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks and protected by assigning usernames to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves should submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Suite 1000, Washington, DC 20002, and include the following information: 1. Full name; 2. Any available information regarding the type of record involved; 3. The address to which the record information should be sent; and 4. You must sign your request. {:.alpha} Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB’s Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **HISTORY:** 55 FR 18949 (May 7, 1990); 77 FR 11534 (Feb. 27, 2012); 81 FR 7106 (Feb. 10, 2016); 85 FR 43654 (July 17, 2020). </div> </li> <!-- FRTIB-8 --> <li id="frtib-8"> <button class="usa-accordion-button" disabled aria-expanded="false" aria-controls="a8"> FRTIB-8 | Retired </button> <div id="a8" class="usa-accordion-content" markdown="1"></div> </li> <!-- FRTIB-9 --> <li id="frtib-9"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a9"> FRTIB-9 | Emergency Notification Files </button> <div id="a9" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43662 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170) **SYSTEM NAME AND NUMBER:** FRTIB-9, Emergency Notification Files. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records are located at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be located in additional locations in connection with cloud-based services and kept at an additional location as backup for Business Continuity purposes. **SYSTEM MANAGER(S):** Chief, Business Continuity and Security Services Division, 77 K Street NE., Suite 1000, Washington, DC 20002, (202) 942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; 44 U.S.C. 3101; E.O. 12656; and Presidential Decision Directive 67. **PURPOSE(S) OF THE SYSTEM:** This system of records is maintained for contacting FRTIB personnel, including FRTIB employees and contractors, and other individuals to respond to all emergencies, including technical, manmade or natural disaster, or other event affecting FRTIB operations, and to contact FRTIB personnel’s emergency contacts in the event of an emergency. Information from this system of records is also used to prepare organizational charts, recall and emergency notification rosters, and directories for business continuity planning purposes, locate individuals on routine and/or emergency matters; locate individuals during medical emergencies, facility evacuations and similar situations involving threats; and similar administrative uses requiring personnel data. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** Civilian and contractor personnel working at the FRTIB located at 77 K Street NE, Washington, DC 20002; former employees; and individuals designated as emergency points of contact. **CATEGORIES OF RECORDS IN THE SYSTEM:** This system of records contains information regarding the following emergency contact information for FRTIB employees, and contractor personnel: Name; organizational office, or organizational name of contractor; title; position and duty status; name of supervisor; any volunteered medical information; office telephone number; government or business e-mail address; home address; home and cell phone numbers; personal email address(es); the identification of essential and non-essential employees; and other personal contact information. This system also contains the following information for the FRTIB employee or contractor’s emergency contact: name; relationship to FRTIB employee or contractor; work address; home address; office telephone number; home and cell phone numbers; and email address(es). **RECORD SOURCE CATEGORIES:** Information is provided by the individual who is the subject of the record. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, 5 U.S.C. 552a(b), and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 3. Routine Use&#8212;Contractors, et al.: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 4. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person’s former area of responsibility. 5. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 6. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 7. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 8. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 9. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 10. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 11. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 12. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. 13. Routine Use&#8212;Testing: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign governmental agencies or multilateral governmental organizations where FRTIB is aware of a need to utilize relevant data for purposes of testing new technology and systems designed to enhance security or identify other violations of law. 14. Routine Use&#8212;Medical Emergency: A record in this system of records may be disclosed to family members, emergency medical personnel, or to law enforcement officials in case of a medical or other emergency involving the subject individual (without the subsequent notification prescribed in 5 U.S.C. 552a(b)(8)). 15. Routine Use&#8212;Breach Mitigation and Notification: A record from this system may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 16. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained electronically in computer databases, including cloud-based services, and on paper in secure facilities in a locked drawer behind a secured-access door. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Records are retrieved by the name of the individual on whom they are maintained, and may also be retrieved by the individual’s title or phone number. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** Records are maintained as long as the individual is an employee or contractor for the Agency. Expired records are destroyed by shredding or purging from the Agency’s electronic recordkeeping systems. **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB’s security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in locked file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks and protected by assigning usernames to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves should submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Suite 1000, Washington, DC 20002, and include the following information: 1. Full name; 2. Any available information regarding the type of record involved; 3. The address to which the record information should be sent; and 4. You must sign your request. {: .alpha} Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB’s Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **HISTORY:** 55 FR 18949 (May 7, 1990); 71 FR 64706 (Nov. 3, 2006); 77 FR 11534 (Feb. 27, 2012); 80 FR 43428 (July 22, 2015); 85 FR 43654 (July 17, 2020). </div> </li> <!-- FRTIB-10 --> <li id="frtib-10"> <button class="usa-accordion-button" disabled aria-expanded="false" aria-controls="a10"> FRTIB-10 | Retired </button> <div id="a10" class="usa-accordion-content" markdown="1"></div> </li> <!-- FRTIB-11 --> <li id="frtib-11"> <button class="usa-accordion-button" disabled aria-expanded="false" aria-controls="a11"> FRTIB-11 | Retired </button> <div id="a11" class="usa-accordion-content" markdown="1"></div> </li> <!-- FRTIB-12 --> <li id="frtib-12"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a12"> FRTIB-12 | Debt Collection Records </button> <div id="a12" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43664 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170). **SYSTEM NAME AND NUMBER:** FRTIB-12, Debt Collection Records. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records are maintained at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be maintained at an additional location for Business Continuity Purposes. **SYSTEM MANAGER:** Director, Office of Participant Services, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002, (202) 942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; 5 U.S.C. 301; 31 U.S.C. 3711(a); and 44 U.S.C. 3101. **PURPOSE(S) OF THE SYSTEM:** The purpose of this system is to maintain a record of individuals and entities that are indebted to the Board, a Federal agency, or a Government corporation including, but not limited to: participants, beneficiaries, and alternate payees of the Thrift Savings Plan; current and former employees of the FRTIB; and individuals who received payments to which they are not entitled. The records ensure that: Appropriate collection action on debtors’ accounts is taking and properly tracked, monies collected are credited, and funds are returned to the Board or appropriate agency at the time the account is collected or closed. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** Records are maintained on individuals and entities that are financially indebted to the Board, including, but not limited to: Participants, beneficiaries, and alternate payees of the Thrift Savings Plan; current and former employees of the FRTIB; individuals who are consultants and vendors to FRTIB; and individuals who received payments to which they are not entitled. **CATEGORIES OF RECORDS IN THE SYSTEM:** Information varies depending on the individual debtor, the type of indebtedness, and the agency or program to which monies are owed. The system of records contains information including but not limited to: (1) Individuals and commercial organizations, such as name, Taxpayer Identification Number (i.e., Social Security Number or Employer Identification Number), business and home addresses, and business and home telephone numbers; (2) the indebtedness, such as the original amount of the debt, the date the debt originated, the amount of the delinquency/default, the date of the delinquency/default, basis of the debt, amounts accrued for interest, penalties, and administrative costs, and payments on the account; (3) actions taken to recover the debt, such as copies of demand letters/invoices, and documents required for the referral of accounts to collection agencies, or for litigation; (4) debtor and creditor agencies, such as name, telephone number, and address of the agency contact; (5) information for location purposes, including information pertaining to child support cases, Mandatory Victims Restitution Act (MVRA) cases, and tax levies; and (6) other relevant records relating to a debt including the amount, status, and history of the debt, and the program under which the debt arose. **RECORD SOURCE CATEGORIES:** Information in this system of records is obtained from subject individuals; the individual entity; the Board; creditor agencies; Federal employing agencies; Government corporations; debt collection agencies or firms; credit bureaus, firms or agencies providing locator services; and Federal, state, and local agencies furnishing identifying information. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, as amended, 5 U.S.C. 552a(b); and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Clearance Processing: A record from this system of records may be disclosed to an appropriate federal, state, local, tribal, foreign, or international agency, if the information is relevant and necessary to a requesting agency's decision concerning the hiring or retention of an individual, or issuance of a security clearance, background investigation, license, contract, grant, or other benefit, or if the information is relevant and necessary to a FRTIB decision concerning the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant or other benefit and when disclosure is appropriate to the proper performance of the official duties of the person making the request. 3. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 4. Routine Use&#8212;Contractors, _et al._: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 5. Routine Use&#8212;Debt Collection: A record from this system of records may be disclosed to the Department of Justice, the Department of Treasury, or to a consumer reporting agency for collection action on any delinquent debt, pursuant to 5 U.S.C. 552a(b)(12). 6. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person's former area of responsibility. 7. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 8. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 9. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 10. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 11. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 12. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 13. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 14. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 15. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. 16. Routine Use&#8212;Collection of Debts, Financial Management Service: A record from this system may be disclosed to the Financial Management Service (FMS) of the Department of the Treasury to allow that agency to act for the Board to enforce collection of delinquent debts owed to the Board or the Thrift Savings Fund. 17. Routine Use&#8212;Collection of Debts, Internal Revenue Service: Debt collection records may be disclosed to the Internal Revenue Service for the purposes of: (1) Effecting an administrative offset against the debtor’s tax refund to recover a delinquent debt owed the Board or the Thrift Savings Fund; or (2) obtaining the mailing address of a taxpayer/debtor in order to locate the taxpayer/debtor to collect or compromise a Federal claim against the taxpayer/debtor. 18. Routine Use&#8212;Collection of Debts, Department of Justice: A record from this system may be disclosed to the Department of Justice for the purpose of litigating to enforce collection of a delinquent debt or to obtain the Department of Justice’s concurrence in a decision to compromise, suspend, or terminate collection action on a debt with a principal amount in excess of $100,000 or such higher amount as the Attorney General may, from time to time, prescribe in accordance with 31 U.S.C. 3711(a). 19. Routine Use&#8212;Collection of Debts, Administrative Offsets: Information contained within this system of records may be disclosed to the Department of the Treasury, Department of Defense, United States Postal Service, another Federal agency, a Government corporation, or any disbursing official of the United States for the purpose of effecting an administrative offset against Federal payments certified to be paid to the debtor to recover a delinquent debt owed to the Board, the Thrift Savings Fund, or another Federal agency or department by the debtor. 20. Routine Use&#8212;Collection of Debts, Voluntary Repayment of Debt: Debt collection information may be disclosed to a creditor Federal agency or Government corporation seeking assistance for the purpose of obtaining voluntary repayment of a debt or implementing Federal employee salary offset or administrative offset in the collection of an unpaid financial obligation. 21. Routine Use&#8212;Collection of Debts, Wage Garnishment: Administrative wage garnishment information may be disclosed to the Treasury Department for the purpose of issuing wage garnishment orders to collect a debt owed to the FRTIB. 22. Routine Use&#8212;Breach Mitigation and Notification: A record from this system may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 23. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. DISCLOSURE TO CONSUMER REPORTING AGENCIES: Debt information concerning claims of the Board and the Thrift Savings Fund may be furnished in accordance with 5 U.S.C. 552a(b)(12) and section 3 of the Debt Collection Act of 1982, as amended (31 U.S.C. 3701 et seq.), to consumer reporting agencies (as defined by the Fair Credit Reporting Act 15 U.S.C. 1681a(f)), to encourage repayment of an overdue debt. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained in paper and electronic form, including on computer databases, all of which are stored in a secure location. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** These records are indexed and retrieved by the names, Social Security numbers, or contact numbers of participants, employees, contractors, or other persons who may receive monies paid to them by the Board. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** Hard-copy records are returned to the Board which has an agreement for servicing and collection of the debt with Financial Management Services. Files are destroyed when 10 years old, unless they are subject to litigation in which case they are destroyed when a court order requiring that the file be retained allows the file to be destroyed or litigation involving the files is concluded. **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB's security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in locked file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks and protected by assigning user IDs to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves must submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Washington, DC 20002, and provide the following information: 1. Full name; 2. Any available information regarding the type of record involved; 3. The address to which the record information should be sent; and 4. You must sign your request. {: .alpha} Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB's Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **HISTORY:** 62 FR 49011 (Sept. 18, 1997); 77 FR 11534 (Feb. 27, 2012); 81 FR 7106 (Feb. 10, 2016). </div> </li> <!-- FRTIB-13 --> <li id="frtib-13"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a13"> FRTIB-13 | Fraud and Forgery Records </button> <div id="a13" class="usa-accordion-content" markdown="1"> **Summary of Purpose** Pursuant to the Privacy Act of 1974, 5 U.S.C. 552a, the Federal Retirement Thrift Investment Board (FRTIB) is proposing to modify its system of records for fraud and forgery records. Records contained in this system are used to investigate potential or actual fraud against TSP participant or beneficiary accounts. FRTIB is modifying this system of records to account for its process for addressing new alerts the Financial Services Information Sharing and Analysis Center (FS-ISAC) sends to FRTIB to better help protect and secure participant account information. **DATES:** This system will become effective upon its publication in today’s Federal Register. FRTIB is not proposing any changes to the routine uses. **ADDRESSES:** You may submit written comments to FRTIB by any one of the following methods: - _Federal [eRulemaking Portal]({{ site.baseurl }}/exit/?idx=145)._ Follow the website instructions for submitting comments. - _Fax_: (202) 942-1676. - _Mail or Hand Delivery:_ Office of General Counsel, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. **FOR FURTHER INFORMATION CONTACT:** Marla Greenberg, Chief Privacy Officer, Federal Retirement Thrift Investment Board, Office of General Counsel, 77 K Street NE, Suite 1000, Washington, DC 20002, (202) 942-1600. For access to any of the FRTIB’s system of records, contact Amanda Haas, FOIA Officer, Office of General Counsel, at the above address and phone number. **SUPPLEMENTARY INFORMATION:** FRTIB is proposing to modify its system of records for fraud and forgery records, entitled, “FRTIB-13, Fraud and Forgery Records.” The proposed changes are necessary because they enable the FRTIB to protect participant accounts based on additional information FRTIB receives from the FS-ISAC, concerning account credentials that may have been compromised. FRTIB is proposing to amend the purpose of the system of records to provide additional context around how the Agency protects participant accounts from fraudulent activity. FRTIB is proposing to change the categories of individuals covered by the system, to include information about participants and beneficiaries who may be actual or potential victims of fraud. Additionally, FRTIB is proposing to modify the category of records in the system to include telephone numbers, IP addresses, and notifications from FS-ISAC, which includes potentially or actually compromised credentials participants use to log into their TSP account online. FRTIB is also proposing a change to record source categories to include FS-ISAC. Finally, FRTIB is proposing technical and clarifying language to conform to the standards established in OMB Circular A-108, but these changes are not substantive in nature. FRTIB is not proposing modifications to its routine uses or exemptions claimed. **Megan Grumbine,** General Counsel and Senior Agency Official for Privacy **SYSTEM NAME:** Fraud and Forgery Records. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records are located at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be kept at an additional location for Business Continuity purposes. **SYSTEM MANAGER:** Supervisory Fraud Specialist, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; and 44 U.S.C. 3101. **PURPOSE(S):** These records are used to inquire into and investigate allegations that a TSP participant, beneficiary, alternate payee, or third party has committed or attempted to commit an act of fraud or forgery relating to a participant or beneficiary account or the Thrift Savings Fund; _to prevent fraud and to protect participant accounts from potential fraud;_ and to collect information to verify allegations that a third party has misappropriated the FRTIB’s (or TSP’s) name, brand, or logos. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** This system of records contains information on Thrift Savings Plan (TSP) participants, beneficiaries, alternate payees, and third party individuals alleged to have committed an act of fraud or forgery relating to participant and beneficiary accounts; and third parties alleged to have misappropriated, or attempted to misappropriate the FRTIB’s (including the TSP’s) name, brand, or logos. _This system of records also contains information about TSP participants and beneficiaries who may be actual or potential victims of fraud._ **CATEGORIES OF RECORDS IN THE SYSTEM:** These records contain the following kinds of information: name, date of birth, _telephone number, IP address,_ and Social Security number of TSP participants, beneficiaries, alternate payees, and third parties alleged to have committed an act of fraud or forgery relating to participant accounts or the Thrift Savings Fund; TSP account information related to the fraud or forgery allegation; information obtained from other agencies as it relates to allegations of fraud or forgery; documentation of complaints and allegations of fraud and forgery; exhibits, statements, affidavits, or records obtained during investigations of fraud, or forgery, court and administrative orders, transcripts, and documents; internal staff memoranda; staff working papers; _notifications from the Financial Services Information Sharing and Analysis Center (FS-ISAC), including credentials used to log into MyAccount that have been potentially or actually compromised;_ and other documents and records related to the investigation of fraud or forgery, including the disposition of the allegations; and reports on the investigation. **RECORD SOURCE CATEGORIES:** Records in this system may be provided by or obtained from the following: persons to whom the information relates when practicable, including TSP participants, beneficiaries, alternate payees, or other third parties; complainants; informants; witnesses; investigators; persons reviewing the allegations; Federal, state and local agencies; _FS-ISAC;_ and investigative reports and records. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND THE PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, as amended, 5 U.S.C. 552a(b); and: 1. A record from this system may be disclosed to the Federal Bureau of Investigation; Department of Justice; Securities and Exchange Commission; Federal Trade Commission; Consumer Financial Protection Bureau; or the Financial Industry Regulatory Authority for further investigation, prosecution, or enforcement. 2. A record from this system may be disclosed to the Secret Service for the purpose of investigating forgery, and to the Department of Justice, when substantiated by the Secret Service. 3. A record pertaining to this system may be disclosed to the current or former employing agency of the participant, beneficiary, alternate payee, or third party alleged to have committed fraud or forgery against a participant account or the Thrift Savings Fund for the purpose of further investigation or administrative action. 4. A record from this system may be disclosed to informants, complainants, or victims to the extent necessary to provide those persons with information and explanations concerning the progress or results of the investigation. 5. Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 6. Breach Mitigation and Notification: Response to Breach of FRTIB Records: A record from this system of records may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records; (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 7. Response to Breach of Other Records: A record from this system of records may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. 8. Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 9. Contractors, et al.: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 10. Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 11. Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate Federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 12. Law Enforcement Intelligence: A record from this system of records may be disclosed to a Federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 13. Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate Federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 14. Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB's outside counsel, other Federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (2) any employee of FRTIB in his or her official capacity, or (3) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (4) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 15. Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 16. NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other Federal Government agencies pursuant to the Federal Records Act. 17. Security Threat: A record from this system of records may be disclosed to Federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained in paper and electronic form, including on computer databases _and cloud-based services_, all of which are _securely_ stored. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Records are retrieved by name or file number. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** Records in this system are destroyed seven years after the case is closed. **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB’s security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in locked file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks and protected by assigning user IDs to individuals needing access to the records and by passwords set by authorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to access records within this system must submit a request pursuant to 5 CFR Part 1630. Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as Power of Attorney, in order for the representative to act on their behalf. **CONTESTING RECORD PROCEDURES:** _See Record Access Procedures above_. **NOTIFICATION PROCEDURES:** _See Record Access Procedures above_. **EXEMPTIONS CLAIMED FOR SYSTEM:** Pursuant to 5 U.S.C. 552a(k)(2), records in this system of records are exempt from the requirements of subsections (c)(3); (d); (e)(1); (e)(4)(G), (H), (I); and (f) of 5 U.S.C. 552a, provided, however, that if any individual is denied any right, privilege, or benefit that he or she would otherwise be entitled to by Federal law, or for which he or she would otherwise be eligible, as a result of the maintenance of these records, such material shall be provided to the individual, except to the extent that the disclosure of the material would reveal the identity of a source who furnished information to the Government with an express promise that the identity of the source would be held in confidence. **HISTORY:** 81 Fed. Reg. 7,106 (Feb. 10, 2016). </div> </li> <!-- FRTIB-14 --> <li id="frtib-14"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a14"> FRTIB-14 | FRTIB Legal Case Files </button> <div id="a14" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43666 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170). **SYSTEM NAME AND NUMBER:** FRTIB-14, Legal Case Files. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records are located at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be located in additional locations for Business Continuity purposes. **SYSTEM MANAGER:** General Counsel, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; and 44 U.S.C. 3301. **PURPOSE(S) OF THE SYSTEM:** The purpose of this system is to assist FRTIB attorneys in providing legal advice to FRTIB personnel on a wide variety of legal issues; to collect the information of any individual who is, or will be, in litigation with the Agency, as well as the attorneys representing the plaintiff(s) or defendant(s), response to claims by employees, former employees, and other individuals; to assist in the settlement of claims against the government; to represent FRTIB during litigation; and to catalogue, investigate, litigate, or otherwise resolve any case or matter handled by the Office of General Counsel. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** Individuals who are participants, beneficiaries, and alternate payees of the Thrift Savings Plan; other individuals who are identified in connection with investigations and/or litigation conducted with regard to FERSA; individuals (including FRTIB employees) who are parties to or witnesses in civil litigation or administrative proceedings involving or concerning FRTIB or its officers or employees (including Special Governmental Employees); individuals who are the subject of a breach of personally identifiable information; individuals who are contractors or potential contractors with FRTIB or are otherwise personally associated with a contract or procurement matter; individuals who receive legal advice from the Office of General Counsel; and other individuals (including current, former, and potential FRTIB employees (including Special Governmental Employees), contractors, interns, externs, and volunteers) who are the subject of or are otherwise connected to an inquiry, investigation, or other matter handled by the Office of General Counsel. **CATEGORIES OF RECORDS IN THE SYSTEM:** Notes, reports, legal opinions and memoranda; settlements; agreements; documentary evidence; claims and records regarding discrimination; correspondence; contracts; contract proposals and other procurement documents; TSP documents; participant, beneficiary, and alternate payee files; initial and final FRTIB determinations of FERSA matters; Freedom of Information Act and Privacy Act requests and appeals, and decisions of those requests and appeals; drafts and legal reviews of proposed personnel actions; personnel records; litigation files; employee relations files; witness statements; summonses and subpoenas; affidavits; court transcripts; discovery requests and responses; and breach reports and supporting documents. **RECORD SOURCE CATEGORIES:** Subject individuals; TSP participants, beneficiaries, and alternate payees; federal government records; current, and former, and potential employees (including Special Government Employees); contractors; interns, externs, and volunteers; the Social Security Administration; court records; articles from publications; and other organizations or individuals with relevant knowledge or information. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, 5 U.S.C. 552a(b), and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Clearance Processing: A record from this system of records may be disclosed to an appropriate federal, state, local, tribal, foreign, or international agency, if the information is relevant and necessary to a requesting agency’s decision concerning the hiring or retention of an individual, or issuance of a security clearance, background investigation, license, contract, grant, or other benefit, or if the information is relevant and necessary to a FRTIB decision concerning the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant or other benefit and when disclosure is appropriate to the proper performance of the official duties of the person making the request. 3. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 4. Routine Use&#8212;Contractors, _et al._: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 5. Routine Use&#8212;Debt Collection: A record from this system of records may be disclosed to the Department of Justice, the Department of Treasury, or to a consumer reporting agency for collection action on any delinquent debt, pursuant to 5 U.S.C. 552a(b)(12). 6. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person’s former area of responsibility. 7. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 8. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 9. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 10. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 11. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 12. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 13. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 14. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 15. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. 16. Routine Use&#8212;Collection of Debts, General: Names, addresses, telephone numbers, and email addresses of employees, former employees, participants, beneficiaries, alternate payees, and information pertaining to debts to the FRTIB may be disclosed to the Department of Treasury, Department of Justice, a credit agency, and a debt collection firm to collect the debt. Disclosure to a debt collection firm shall be made only under a contract that binds any such contractor or employee of such contractor to the criminal penalties of the Privacy Act. 17. Routine Use&#8212;General Investigations, Third Parties: Information may be provided to third parties during the course of an investigation to the extent necessary to obtain information pertinent to the investigation. 18. Routine Use&#8212;International Treaties or Conventions: A record relating to a case or matter may be disseminated to a foreign country pursuant to an international treaty or convention entered into and ratified by the United States or to an executive agreement. 19. Routine Use&#8212;Foreign Country, Civil or Criminal Proceedings: A record may be disseminated to a foreign country, through the United States Department of State or directly to the representative of such country, to the extent necessary, to assist such country in civil or criminal proceedings in which the United States or one of its officers or agents has an interest. 20. Routine Use&#8212;Breach Mitigation and Notification: A record from this system may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 21. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. DISCLOSURE TO CONSUMER REPORTING AGENCIES: Information from this system of records may be disclosed to a consumer reporting agency in accordance with 31 U.S.C. 3711(e). **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained electronically in computer databases, including cloud-based services, and on paper in secure facilities in a locked drawer behind a secured-access door. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Records are retrieved by the name of the individual on whom they are maintained, and may also be retrieved by case number. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** Records are maintained in accordance with the General Records Retention Schedules issued by the National Archives and Records Administration (NARA) or an FRTIB records disposition schedule. **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB's security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks, including cloud-based services, and are protected by assigning user IDs to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves must submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Washington, DC 20002, and provide the following information: 1. Full name; 2. Any available information regarding the type of record involved; 3. The address to which the record information should be sent; and 4. You must sign your request. {: .alpha} Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB's Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** Pursuant to 5 U.S.C. 552a(k)(2), records from this system are exempt from the requirements of subsections (c)(3); (d); (e)(1); (e)(4)(G), (H), (I); and (f) of 5 U.S.C. 552a, provided, however, that if any individual is denied any right, privilege, or benefit that he or she would otherwise be entitled to by Federal law, or for which he or she would otherwise be eligible, as a result of the maintenance of these records, such material shall be provided to the individual, except to the extent that the disclosure of the material would reveal the identity of a source who furnished information to the Government with an express promise that the identity of the source would be held in confidence. **DISCLOSURE TO CONSUMER REPORTING AGENCIES:** Information from this system of records may be disclosed to a consumer reporting agency in accordance with 31 U.S.C. 3711(e). **HISTORY:** 80 FR 43428 (July 22, 2015). </div> </li> <!-- FRTIB-15 --> <li id="frtib-15"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a15"> FRTIB-15 | Internal Investigations of Harassment and Hostile Work Environment Allegations </button> <div id="a15" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43669 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170). **SYSTEM NAME AND NUMBER:** FRTIB-15, Internal Investigations of Harassment and Hostile Work Environment Allegations. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records are located at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be located in additional locations for Business Continuity purposes. **SYSTEM MANAGER:** Human Resources Officer, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; 42 U.S.C. 2000e et seq.; and 44 U.S.C. 3101. **PURPOSE(S) OF THE SYSTEM:** This system of records is maintained for the purpose of upholding FRTIB's policy to provide for a work environment free from all forms of harassment, including sexual harassment, and harassment on the basis of race, color, gender, national origin, religion, sexual orientation, age, genetic information, reprisal, parental status, or disability. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** Current or former FRTIB employees (including Special Government Employees), contractors, interns, externs, and volunteers who have filed a complaint or report of harassment or hostile work environment, or have been accused of harassing conduct; and witnesses or potential witnesses. **CATEGORIES OF RECORDS IN THE SYSTEM:** This system of records contains all documents related to a complaint or report of harassment, which may include the name, position, grade, and supervisor(s) of the complainant and the accused; the complaint; witness statements; interview notes; legal memoranda; reports of investigation; final decisions and corrective actions taken; and related correspondence and exhibits. **RECORD SOURCE CATEGORIES:** Subject individuals; supervisors and other FRTIB employees with knowledge; agency EEO and human resources specialists; employee relations staff; FRTIB attorneys; outside counsel retained by subject individuals; and medical professionals. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, 5 U.S.C. 552a(b), and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Clearance Processing: A record from this system of records may be disclosed to an appropriate federal, state, local, tribal, foreign, or international agency, if the information is relevant and necessary to a requesting agency's decision concerning the hiring or retention of an individual, or issuance of a security clearance, background investigation, license, contract, grant, or other benefit, or if the information is relevant and necessary to a FRTIB decision concerning the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant or other benefit and when disclosure is appropriate to the proper performance of the official duties of the person making the request. 3. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 4. Routine Use&#8212;Contractors, _et al._: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 5. Routine Use&#8212;Debt Collection: A record from this system of records may be disclosed to the Department of Justice, the Department of Treasury, or to a consumer reporting agency for collection action on any delinquent debt, pursuant to 5 U.S.C. 552a(b)(12). 6. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person's former area of responsibility. 7. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 8. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 9. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 10. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 11. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 12. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 13. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 14. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 15. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. 16. Routine Use&#8212;Complainant, Witnesses: Disclosure of information from this system of records about an investigation that may have been conducted may be made to the complaining party; the alleged harasser; and to a limited number of witnesses when the purpose of the disclosure is both relevant and necessary and is compatible with the purpose for which the information was collected. 17. Routine Use&#8212;Breach Mitigation and Notification: A record from this system may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 18. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained electronically in computer databases, including cloud-based services, and on paper in secure facilities in a locked drawer behind a secured-access door. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Records are retrieved by the name of the individual on whom they are maintained, and may also be retrieved by case number. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** Records are maintained in accordance with the General Records Retention Schedules issued by the National Archives and Records Administration (NARA) or an FRTIB records disposition schedule. **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB's security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks, including cloud-based services, and are protected by assigning user IDs to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves must submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Washington, DC 20002, and provide the following information: 1. Full name; 2. Any available information regarding the type of record involved; 3. The address to which the record information should be sent; and 4. You must sign your request. {: .alpha} Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB's Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** Pursuant to 5 U.S.C. 552a(k)(2), records in this system are exempt from the requirements of subsections (c)(3); (d); (e)(1); (e)(4)(G), (H), (I); and (f) of 5 U.S.C. 552a, provided, however, that if any individual is denied any right, privilege, or benefit that he or she would otherwise be entitled to by Federal law, or for which he or she would otherwise be eligible, as a result of the maintenance of these records, such material shall be provided to the individual, except to the extent that the disclosure of the material would reveal the identity of a source who furnished information to the Government with an express promise that the identity of the source would be held in confidence. **HISTORY:** 80 FR 43428 (July 22, 2015); 85 FR 43654 (July 17, 2020). </div> </li> <!-- FRTIB-16 --> <li id="frtib-16"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a16"> FRTIB-16 | Congressional Correspondence Files </button> <div id="a16" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43671 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170). **SYSTEM NAME AND NUMBER:** FRTIB-16, Congressional Correspondence Files. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records are maintained at the Federal Retirement Thrift Investment Board, 77 K Street NE, Washington, DC 20002. Records may also be maintained at an additional location for Business Continuity Purposes. **SYSTEM MANAGER(S):** Director, Office of External Affairs, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; 5 U.S.C. 301; and 44 U.S.C. 3101. **PURPOSE(S) OF THE SYSTEM:** This system of records is maintained to catalog and respond to correspondence received from congressional offices. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** Individuals who submit inquiries, complaints, comments, or other correspondence to FRTIB, and the responding party on behalf of FRTIB. **CATEGORIES OF RECORDS IN THE SYSTEM:** Categories of records in this system include, but are not limited to the following information about individuals who have corresponded with FRTIB: Name; dates of birth; Social Security numbers; TSP account numbers; home and business address; email address; personal and business telephone numbers; who the correspondence is about; incoming correspondence; FRTIB's response; the FRTIB responder's name and business information; additional unsolicited personal information provided by the individual; and other related materials. **RECORD SOURCE CATEGORIES:** Information used to compile records in this system is taken from incoming correspondence and FRTIB responses to incoming correspondence from congressional offices. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, as amended, 5 U.S.C. 552a(b); and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 3. Routine Use&#8212;Contractors, _et al._: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 4. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person's former area of responsibility. 5. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 6. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 7. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 8. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 9. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 10. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 11. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 12. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 13. Routine Use&#8212;Referral of Correspondence: A record from this system of records may be disclosed to another Federal agency to refer correspondence or refer to correspondence, given the nature of the issue. 14. Routine Use&#8212;News Media and Public, Public Interest: Information in this system of records may be disclosed to the news media and the public, with the approval of the Senior Agency Official for Privacy, in consultation with counsel, when there exists a legitimate public interest in the disclosure of the information; when disclosure is necessary to preserve confidence in the integrity of FRTIB; or when it is necessary to demonstrate the accountability of FRTIB’s officers, employees, or individuals covered by this system, except to the extent it is determined that the release of the specific information in the context of a particular case would constitute an unwarranted invasion of personal privacy. 15. Routine Use&#8212;Breach Mitigation and Notification: A record from this system may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 16. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained in paper and electronic form, including on computer databases, all of which are stored in a secure location. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Records may be retrieved by individual name; the name of the Member of Congress requesting a response; and the date of the correspondence. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** Records are maintained in accordance with the General Records Retention Schedules issued by the National Archives and Records Administration (NARA) or an FRTIB records disposition schedule. **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB’s security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in locked file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks and protected by assigning usernames to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves must submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Washington, DC 20002, and provide the following information: 1. Full name; 2. Any available information regarding the type of record involved; 3. The address to which the record information should be sent; and 4. You must sign your request. {: .alpha} Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB's Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **HISTORY:** 81 FR 7106 (Feb. 10, 2016); 85 FR 43654 (July 17, 2020). </div> </li> <!-- FRTIB-17 --> <li id="frtib-17"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a17"> FRTIB-17 | Telework and Alternative Worksite Records </button> <div id="a17" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43673 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170). **SYSTEM NAME AND NUMBER:** FRTIB-17, Telework and Alternative Work Schedule Records. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records are maintained at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be maintained at an additional location for Business Continuity Purposes. **SYSTEM MANAGER(S):** Human Resources Officer, 77 K Street NE, Suite 1000, Washington, DC 20002. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; 5 U.S.C. 301; 5 U.S.C. 6120; and 44 U.S.C. 3101. **PURPOSE(S) OF THE SYSTEM:** The purpose of this system of records is to collect and maintain records on prospective, current, and former FRTIB employees who have participated in, presently participate in, or have sought to participate in FRTIB's Telework Program. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** Prospective, current, and former FRTIB employees who have been granted or denied authorization to participate in FRTIB's Telework Program to work at an alternative worksite apart from their official FRTIB duty station. **CATEGORIES OF RECORDS IN THE SYSTEM:** Name, position title, grade level, job series, and office name; official FRTIB duty station address and telephone number; alternative worksite address and telephone number(s); date telework agreement received and approved/denied; telework request and approval form; telework agreement; self-certification home safety checklist, and supervisor-employee checklist; type of telework requested (e.g., situational or core); regular work schedule; telework schedule; approvals/disapprovals; description and list of government-owned equipment and software provided to the teleworker; mass transit benefits received through FRTIB's mass transit subsidy program; parking subsidies received through FRTIB's subsidized parking program; and any other miscellaneous documents supporting telework. **RECORD SOURCE CATEGORIES:** Subject individuals; subject individuals' supervisors. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, as amended, 5 U.S.C. 552a(b); and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 3. Routine Use&#8212;Contractors, _et al._: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 4. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person's former area of responsibility. 5. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 6. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 7. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 8. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 9. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 10. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 11. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 12. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 13. Routine Use&#8212;Medical Professionals: A record from this system may be disclosed to medical professionals to obtain information about an employee’s medical background necessary to grant or deny approval of medical telework. 14. Routine Use&#8212;Emergency Preparedness: A record from this system may be disclosed to federal, state, or local governments during actual emergencies, exercises, or Business Continuity Purpose tests for emergency preparedness and disaster recovery training exercises. 15. Routine Use&#8212;Report of Injury, Department of Labor: A record from this system may be disclosed to the Department of Labor when an employee is injured when working at home while in the performance of normal duties. 16. Routine Use&#8212;Telework Survey, Office of Personnel Management: A record from this system may be disclosed to the Office of Personnel Management (OPM) for use in its Telework Survey to provide consolidated data on participation in FRTIB’s Telework Program. 17. Routine Use&#8212;Third-Parties, Mediation/Alternative Dispute Resolution: A record from this system of records may be disclosed to appropriate third-parties contracted by FRTIB to facilitate mediation or other alternate dispute resolution procedures or programs. 18. Routine Use&#8212;Breach Mitigation and Notification: A record from this system may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 19. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained in paper and electronic form, including on computer databases, all of which are stored in a secure location. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Records are retrieved by any one or more of the following: Employee name; and the office in which the employee works, will work, or previously worked. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** Records are maintained in accordance with the General Records Retention Schedule 1, item 42, issued by the National Archives and Records Administration (NARA). **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB's security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in locked file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks and protected by assigning user IDs to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves must submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Washington, DC 20002, and provide the following information: 1. Full name; 2. Any available information regarding the type of record involved; 3. The address to which the record information should be sent; and 4. You must sign your request. {: .alpha} Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB's Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **HISTORY:** 81 FR 7106 (Feb. 10, 2016); 85 FR 43654 (July 17, 2020). </div> </li> <!-- FRTIB-18 --> <li id="frtib-18"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a18"> FRTIB-18 | Reasonable Accommodation Records </button> <div id="a18" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43675 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170). **SYSTEM NAME AND NUMBER:** FRTIB-18, Reasonable Accommodation Records. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records are maintained at the Federal Retirement Thrift Investment Board, 77 K Street NE, Washington, DC 20002. Records may also be maintained at an additional location for Business Continuity Purposes. **SYSTEM MANAGER:** Human Resources Officer, 77 K Street NE, Washington, DC 20002. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; 5 U.S.C. 301; 42 U.S.C. 12101 et seq.; 44 U.S.C. 3101; Executive Order 13164 (July 28, 2000); and Executive Order 13548 (July 10, 2010). **PURPOSE(S) OF THE SYSTEM:** The purpose of this system is to: (1) Allow FRTIB to collect and maintain records on prospective, current, and former employees with disabilities who request or receive a reasonable accommodation by FRTIB; (2) to track and report the processing of requests for FRTIB-wide reasonable accommodations to comply with applicable laws and regulations; and (3) to preserve and maintain the confidentiality of medical information submitted by or on behalf of applicants or employees requesting a reasonable accommodation. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** Prospective, current, and former FRTIB employees who request and/or receive a reasonable accommodation for a disability; and authorized individuals or representatives (e.g., family members or attorneys) who file a request for a reasonable accommodation on behalf of a prospective, current, or former employee. **CATEGORIES OF RECORDS IN THE SYSTEM:** Name and employment information of employees needing an accommodation; requestor's name and contact information (if different than the employee who needs an accommodation); date request was initiated; information concerning the nature of the disability and the need for accommodation, including appropriate medical documentation; details of the accommodation request, such as: Type of accommodation requested, how the requested accommodation would assist in job performance, the sources of technical assistance consulted in trying to identify alternative reasonable accommodation, any additional information provided by the requestor related to the processing of the request, and whether the request was approved or denied, and whether the accommodation was approved for a trial period; and notification(s) to the employee and his/her supervisor(s) regarding the accommodation. **RECORD SOURCE CATEGORIES:** Subject individuals; subject individuals' supervisors. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, as amended, 5 U.S.C. 552a(b); and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Clearance Processing: A record from this system of records may be disclosed to an appropriate federal, state, local, tribal, foreign, or international agency, if the information is relevant and necessary to a requesting agency’s decision concerning the hiring or retention of an individual, or issuance of a security clearance, background investigation, license, contract, grant, or other benefit, or if the information is relevant and necessary to a FRTIB decision concerning the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant or other benefit and when disclosure is appropriate to the proper performance of the official duties of the person making the request. 3. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 4. Routine Use&#8212;Contractors, _et al._: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 5. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person's former area of responsibility. 6. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 7. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 8. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 9. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 10. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 11. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 12. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 13. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 14. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. 15. Routine Use&#8212;Medical Professionals, Reasonable Accommodation Documentation: A record from this system of records may be disclosed to physicians or other medical professionals to provide them with or obtain from them the necessary medical documentation and/or certification for reasonable accommodations. 16. Routine Use&#8212;Federal Agencies, Equal Employment and Reasonable Accommodation Issues: A record from this system of records may be disclosed to another federal agency or commission with responsibility for labor or employment relations or other issues, including equal employment opportunity and reasonable accommodation issues, when that agency or commission has jurisdiction over reasonable accommodation issues. 17. Routine Use&#8212;Federal Agencies, Reasonable Accommodation Requirements: A record from this system of records may be disclosed to the Department of Labor (DOL), Office of Personnel Management (OPM), Equal Employment Opportunity Commission (EEOC), or Office of Special Counsel (OSC) to obtain advice regarding statutory, regulatory, policy, and other requirements related to reasonable accommodation. 18. Routine Use&#8212;Mediation/Alternative Dispute Resolution: A record from this system of records may be disclosed to appropriate third-parties contracted by the Agency to facilitate mediation or other alternative dispute resolution procedures or programs. 19. Routine Use&#8212;Department of Defense, Procurement of Assistive Technologies: A record from this system of records may be disclosed to the Department of Defense (DOD) for the purpose of procuring assistive technologies and services through the Computer/Electronic Accommodation Program in response to a request for reasonable accommodation. 20. Routine Use&#8212;Breach Mitigation and Notification: A record from this system of records may be disclosed to appropriate agencies, entities, and persons when: (1) FRTIB suspects or has confirmed that the security or confidentiality of information in the system of records has been compromised; (2) FRTIB has determined that as a result of the suspected or confirmed compromise there is a risk of harm to economic or property interests, identity theft or fraud, or harm to the security or integrity of this system or other systems or programs (whether maintained by FRTIB or another agency or entity) that rely upon the compromised information; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with the FRTIB's efforts to respond to the suspected or confirmed compromise and prevent, minimize, or remedy such harm. 21. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained in paper and electronic form, including on computer databases, all of which are stored in a secure location. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Records are retrieved by any one or more of the following: employee name or assigned case number. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** These records are maintained in accordance with the General Records Retention Schedule 1, item 24, issued by the National Archives and Records Administration (NARA). **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB's security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in locked file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks and protected by assigning user IDs to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves must submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Washington, DC 20002, and provide the following information: 1. Full name; 2. Any available information regarding the type of record involved; 3. The address to which the record information should be sent; and 4. You must sign your request. {: .alpha} Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB's Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **DISCLOSURE TO CONSUMER REPORTING AGENCIES:** None. **HISTORY:** 81 FR 7106 (Feb. 10, 2016); 85 FR 43654 (July 17, 2020). </div> </li> <!-- FRTIB-19 --> <li id="frtib-19"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a19"> FRTIB-19 | Freedom of Information Act Records </button> <div id="a19" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 43654, 43677 (July 21, 2020)]({{ site.baseurl }}/exit/?idx=170). **SYSTEM NAME AND NUMBER:** FRTIB-19, Freedom of Information Act Records. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records in this system are maintained at the Federal Retirement Thrift Investment Board, 77 K Street NE, Washington, DC 20002. Records may be maintained at an additional location for Business Continuity Purposes. **SYSTEM MANAGER:** Chief FOIA Officer, Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002, (202) 942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; 5 U.S.C. 552; and 44 U.S.C. 3101. **PURPOSE(S) OF THE SYSTEM:** The purpose of this system is to support the processing of record access requests made pursuant to the FOIA, whether FRTIB receives such requests directly from the requestor or via referral from another agency. In addition, this system is used to support litigation arising from such requests and appeals, and to assist FRTIB in carrying out any other responsibilities under the FOIA. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** This system of records covers all individuals who submit requests pursuant to the Freedom of Information Act (FOIA); individuals whose requests and/or records have been referred to FRTIB by other agencies; attorneys or other persons representing individuals submitting such requests and appeals; individuals who are the subjects of such requests and appeals; individuals who file litigation based on their requests; Department of Justice (DOJ) and other government litigators; and/or FRTIB employees assigned to handle such requests or appeals. **CATEGORIES OF RECORDS IN THE SYSTEM:** Records in this system include, but are not limited to: (1) Records received, created, or compiled in processing FOIA requests or appeals, including original requests and appeals, intra- or inter-agency memoranda, referrals, correspondence notes, fee schedules, assessments, cost calculations, and other documentation related to the referral and/or processing of the FOIA request or appeal, correspondence with the individuals or entities that submitted the requests, and copies of requested records; (2) the type of information in the records may include requestors' and their attorneys' or representatives' contact information, the contact information of FRTIB employees, the name of the individual subject of the request or appeal, fee determinations, unique case identifier, and other identifiers provided by a requestor about him or herself or about the individual whose records are requested. **RECORD SOURCE CATEGORIES:** Records are obtained from those individuals who submit requests and administrative appeals pursuant to the FOIA or who file litigation regarding such requests and appeals; the agency record keeping systems searched in the process of responding to such requests and appeals; FRTIB employees assigned to handle such requests, appeals, and/or litigation; other agencies or entities that have referred to FRTIB requests concerning FRTIB records, or that have consulted with FRTIB regarding handling of particular requests; and submitters or subjects of records or information that have provided assistance to FRTIB in making access or amendment determinations. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, as amended, 5 U.S.C. 552a(b); and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Clearance Processing: A record from this system of records may be disclosed to an appropriate federal, state, local, tribal, foreign, or international agency, if the information is relevant and necessary to a requesting agency’s decision concerning the hiring or retention of an individual, or issuance of a security clearance, background investigation, license, contract, grant, or other benefit, or if the information is relevant and necessary to a FRTIB decision concerning the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant or other benefit and when disclosure is appropriate to the proper performance of the official duties of the person making the request. 3. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 4. Routine Use&#8212;Contractors, et al.: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 5. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel-related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person’s former area of responsibility. 6. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 7. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 8. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 9. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 10. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (b) any employee of FRTIB in his or her official capacity, or (c) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (d) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 11. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 12. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 13. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 14. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. 15. Routine Uses—Federal Agencies, FOIA Processing: A record from this system of records may be disclosed to a federal agency or other federal entity that furnished the record or information for the purpose of permitting that agency or entity to make a decision regarding access to or correction of the record or information, or to a federal agency or entity for purposes of providing guidance or advice regarding the handling of a particular request. 16. Routine Uses—Department of Justice, Advice: A record from this system of records may be disclosed to the Department of Justice (DOJ) to obtain advice regarding statutory and other requirements under the FOIA. 17. Routine Use&#8212;OGIS, FOIA Responsibilities: A record from this system of records may be disclosed to the National Archives and Records Administration, Office of Government Information Services (OGIS), to the extent necessary to fulfill its responsibilities in 5 U.S.C. 552(h) to review administrative agency policies, procedures, and compliance with the FOIA, and to facilitate OGIS’s offering of mediation services to resolve disputes between persons making FOIA requests and administrative agencies. 18. Routine Use&#8212;Breach Mitigation and Notification: A record from this system may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records, (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 19. Routine Use&#8212;Response to Breach of Other Records: A record from this system may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained in paper and electronic form, including on computer databases, all of which are stored in a secure location. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Records are retrieved by any one or more of the following: The name of the requestor; the number assigned to the request or appeal; and in some instances, the name of the attorney representing the requestor or appellant, and/or the name of an individual who is the subject of such a request or appeal. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** Records are retained and disposed of in accordance with the General Records Schedule 4.2, item 020, issued by the National Archives and Records Administration (NARA). **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB's security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Paper records are stored in locked file cabinets in areas of restricted access that are locked after office hours. Electronic records are stored on computer networks and protected by assigning user IDs to individuals needing access to the records and by passwords set by unauthorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to determine whether this system of records contains information about themselves must submit a written request to the FOIA Officer, FRTIB, 77 K Street NE, Washington, DC 20002, and provide the following information: 1. Full name; 2. Any available information regarding the type of record involved; 3. The address to which the record information should be sent; and 4. You must sign your request. {: .alpha} Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. Individuals requesting access must also comply with FRTIB's Privacy Act regulations regarding verification of identity and access to such records, available at 5 CFR part 1630. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **DISCLOSURE TO CONSUMER REPORTING AGENCIES:** None. **HISTORY:** 81 FR 7106 (Feb. 10, 2016); 85 FR 43654 (July 17, 2020). </div> </li> <!-- FRTIB-20 --> <li id="frtib-20"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a20"> FRTIB-20 | Communications, Education, and Outreach Materials </button> <div id="a20" class="usa-accordion-content" markdown="1"> **SUMMARY**: Pursuant to the Privacy Act of 1974, [5 U.S.C. 552a]({{ site.baseurl }}/exit/?idx=156), the Federal Retirement Thrift Investment Board (FRTIB) is proposing to establish a new system of records. Records contained in this system will be used to educate participants about various aspects of the TSP. **DATES**: This system will become effective upon its publication in today’s **Federal Register**, with the exception of the routine uses, which are effective January 10, 2019. FRTIB invites written comments on the routine uses or other aspects of this system of records. Submit any comments by January 10, 2019. **ADDRESSES**: You may submit written comments to FRTIB by any one of the following methods: * _Federal eRulemaking Portal_: [https://www.regulations.gov]({{ site.baseurl }}/exit/?idx=145). Follow the website instructions for submitting comments. * _Fax_: (202) 942-1676. * _Mail or Hand Delivery_: Office of General Counsel, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. **FOR FURTHER INFORMATION CONTACT**: Marla Greenberg, Chief Privacy Officer, Federal Retirement Thrift Investment Board, Office of General Counsel, 77 K Street NE, Suite 1000, Washington, DC 20002, (202) 942-1600. For access to any of the FRTIB’s systems of records, contact Amanda Haas, FOIA Officer, Office of General Counsel, at the above address and phone number. **SUPPLEMENTARY INFORMATION**: FRTIB is proposing to establish a new system of records entitled, “FRTIB-20, Communications, Education, and Outreach Materials.” The proposed system of records is necessary to assist FRTIB’s Office of Communications and Education in effectively educating and communicating with Thrift Savings Plan (TSP) participants and other individuals. Files maintained as part of FRTIB-20 include: information about TSP participants and other individuals who receive educational messages from FRTIB or who have otherwise corresponded with FRTIB, including names, personal and business phone numbers, mailing addresses, email addresses, and social media handles; aggregated data and FRTIB analysis of participant behavior; incoming feedback and other correspondence; FRTIB’s response; the FRTIB responder’s name and business information; additional unsolicited personal information provided by individuals; video recordings of volunteer participants; and related materials. FRTIB is proposing to add sixteen routine uses to apply to FRTIB-20. **Megan Grumbine**, _General Counsel and Senior Agency Official for Privacy_ **SYSTEM NAME AND NUMBER**: FRTIB-20, Communications, Education, and Outreach Materials. **SECURITY CLASSIFICATION**: Unclassified. **SYSTEM LOCATION**: Records are located at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be maintained at additional locations for Business Continuity purposes. **SYSTEM MANAGER**: Director, Office of Communications and Education, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002, or by phone by calling (202) 942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM**: [5 U.S.C. 8474]({{ site.baseurl }}/exit/?idx=157). **PURPOSE OF THE SYSTEM**: The purpose of the system is to educate TSP participants and other individuals about the TSP; to track and analyze aggregated activity to determine the effectiveness of targeted outreach campaigns; and to solicit feedback regarding FRTIB education and outreach efforts. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM**: TSP participants; individuals interested in TSP updates or educational events; and individuals who wish to provide feedback on TSP outreach efforts, including targeted mailings, e-mail campaigns, educational events, social media accounts, and focus groups. **CATEGORIES OF RECORDS IN THE SYSTEM**: Records in this system include, but are not limited to records received, created, or compiled through FRTIB social media accounts, educational outreach efforts, educational events, requests for feedback, and other communications. The type of information in the records may include the names and contact information of the data subject, including mailing addresses, email addresses, phone numbers, and social media handles, of TSP participants or other individuals interested in the TSP; aggregated participant activity data, and FRTIB analysis of participant behavior following targeted communications from FRTIB; feedback on FRTIB communications; FRTIB’s response; the name and business information of FRTIB employees; additional unsolicited personal information provided by individuals; and video or audio recordings of participants and others who voluntarily participate in FRTIB’s educational campaigns or events. **RECORD SOURCE CATEGORIES**: Information in this system is obtained from TSP participant accounts; individuals who sign up to receive email or SMS/text message updates and educational materials from FRTIB; and individuals who interact with the FRTIB through various social media sites or as a result of other educational outreach efforts. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES**: Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, as amended, 5 U.S.C. 552a(b); and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Breach Mitigation and Notification: Response to Breach of FRTIB Records: A record from this system of records may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records; (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 3. Routine Use&#8212;Response to Breach of Other Records: A record from this system of records may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. 4. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 5. Routine Use&#8212;Contractors, et al.: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 6. Routine Use&#8212;Former Employees: A record from this system of records may be disclosed to a former employee of the FRTIB, in accordance with applicable regulations, for purposes of responding to an official inquiry by a federal, state, or local government entity or professional licensing authority; or facilitating communications with a former employee that may be necessary for personnel- related or other official purposes where the FRTIB requires information or consultation assistance from the former employee regarding a matter within that person's former area of responsibility. 7. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 8. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 9. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 10. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 11. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB's outside counsel, other federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (2) any employee of FRTIB in his or her official capacity, or (3) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (4) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 12. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 13. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other federal government agencies pursuant to the Federal Records Act. 14. Routine Use&#8212;Redress: A record from this system of records may be disclosed to a federal, state, tribal, local, international, or foreign government agency or entity for the purpose of consulting with that agency or entity: (1) To assist in making a determination regarding redress for an individual in connection with the operations of a FRTIB program; (2) for the purpose of verifying the identity of an individual seeking redress in connection with the operations of a FRTIB program; or (3) for the purpose of verifying the accuracy of information submitted by an individual who has requested such redress on behalf of another individual. 15. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. 16. A record from this system may be shared with other Federal agencies to register and notify individuals regarding TSP-related educational events. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS**: Records are maintained in paper and electronic form, including on computer databases and cloud-based services, all of which are securely stored. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS**: Records are retrieved by name, account number, email address, phone number, social media handle, demographics, or other unique identifier of the individual about whom they are maintained. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS**: These records are maintained in accordance with General Records Schedules 6.4 (Public Affairs Records) and 6.5 (Public Customer Service Records) issued by the National Archives and Records Administration (NARA). **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS**: FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB's security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. **RECORD ACCESS PROCEDURES:** Individuals seeking to access records within this system must submit a request pursuant to [5 CFR part 1630]({{ site.baseurl }}/exit/?idx=158). Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **HISTORY:** None. </div> </li> <!-- FRTIB-21 --> <li id="frtib-21"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a21"> FRTIB-21 | Identity, Credential and Access Management (ICAM) </button> <div id="a21" class="usa-accordion-content" markdown="1"> **Federal Register** [84 FR 43600 (Aug. 21, 2019))]({{ site.baseurl }}/exit/?idx=128). **SUMMARY**: Pursuant to the Privacy Act of 1974, the Federal Retirement Thrift Investment Board (FRTIB) proposes to establish a new system of records. Records contained in this system will be used to implement Identity, Credential, and Access Management (ICAM) capabilities at the Agency. ICAM manages digital identities, credentials, and access controls for FRTIB applications and systems. **DATES**: This system will become effective upon its publication in today’s Federal Register, with the exception of the routine uses which will be effective on September 20, 2019. FRTIB invites written comments on the routine uses and other aspects of this system of records. Submit any comments by September 20, 2019. **ADDRESSES**: You may submit written comments to FRTIB by any one of the following methods: * _Federal eRulemaking Portal_: [https://www.regulations.gov]({{ site.baseurl }}/exit/?idx=145). Follow the website instructions for submitting comments. * _Fax_: (202) 942-1676. * _Mail or Hand Delivery_: Office of General Counsel, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. **FOR FURTHER INFORMATION CONTACT**: Marla Greenberg, Chief Privacy Officer, Federal Retirement Thrift Investment Board, Office of General Counsel, 77 K Street NE, Suite 1000, Washington, DC 20002, (202) 942-1600. For access to any of the FRTIB’s systems of records, contact Amanda Haas, FOIA Officer, Office of General Counsel, at the above address and phone number. **SUPPLEMENTARY INFORMATION**: FRTIB proposes to establish a new system of records entitled, &#8220;FRTIB-21, Identity, Credential and Access Management (ICAM).&#8221; ICAM manages digital identities, credentials, and access controls for FRTIB applications and systems. ICAM is necessary to vet potential users; link employees and contractors to digital identity accounts; provision and de-provision accounts and access; and to monitor identity credentials, access to systems and data, and related risks. The proposed system of records implements ICAM capabilities across all FRTIB IT systems. ICAM supports the following seven key functions of the ICAM Framework as defined by the Federal Chief Information Officer (CIO) Council: digital identity, credentialing, authentication, cryptography, auditing and reporting, authorization and access, and privilege management. FRTIB’s ICAM’s capabilities are also aligned with the Federal CIO Council’s Federal Identity, Credential, and Access Management (FICAM) procedures, available at, [https://www.idmanagement.gov/wp-content/uploads/sites/1171/uploads/FICAM_Roadmap_and_Implem_Guid.pdf]({{ site.baseurl }}/exit/?idx=169){:rel="nofollow"}. FRTIB proposes to apply thirteen routine uses to FRTIB-21. **Megan Grumbine**, _General Counsel and Senior Agency Official for Privacy_ **SYSTEM NAME AND NUMBER**: FRTIB-21, Identity, Credential and Access Management (ICAM). **SECURITY CLASSIFICATION**: Unclassified. **SYSTEM LOCATION**: Records are located at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be maintained at additional locations for Business Continuity purposes. **SYSTEM MANAGER**: Director, Office of Technology Services, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002, 202-942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM**: [5 U.S.C. 8474]({{ site.baseurl }}/exit/?idx=157); and 44 U.S.C. Chapter 35. **PURPOSE(S) OF THE SYSTEM**: ICAM employs a comprehensive management approach for digital identities and associated attributes, credentials (including PKI, PIV, other authentication tokens), and access controls. It centralizes a consistent, integrated method for managing the identities of individuals and devices requiring logical access and for enforcing logical access privileges to FRTIB resources for all FRTIB employees and contractors. ICAM protects FRTIB information and systems by ensuring that only the appropriate users have access to information systems, personally identifiable information (PII), and other sensitive data based on the principles of least privilege and need-to-know. ICAM manages the identities of individuals that access FRTIB logical resources, authorizes users’ permissions, enforces access controls for IT systems and information, and audits access to and the use of sensitive information and functions. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM**: FRTIB employees and contractors. **CATEGORIES OF RECORDS IN THE SYSTEM**: Records in this system include: first name, middle name, last name, personal phone number, personal e-mail address, social security number, date of birth, place of birth, current address, business address, business e-mail address, business phone number, employment information (e.g., employment type, manager status, domain administrator status, hire date, contract end date), user name, user name creation date, IP address, background investigation data including Electronic Questionnaires for Investigations Processing (e-QIP) review and release date, fingerprint submission and completion date, OPM investigation type, investigation review and completion date, PIV card information, completion date for required training, and completion date for required documentation (e.g., rules of behavior, non-disclosure agreement). **RECORD SOURCE CATEGORIES**: FRTIB obtains records within this system from FRTIB employees and contractors and from OPM through access to e-QIP. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES**: Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, as amended, 5 U.S.C. 552a(b); and: 1. Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Breach Mitigation and Notification: Response to Breach of FRTIB Records: A record from this system of records may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records; (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 3. Response to Breach of Other Records: A record from this system of records may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. 4. Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 5. Contractors, et al.: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 6. Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 7. Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate Federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 8. Law Enforcement Intelligence: A record from this system of records may be disclosed to a Federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 9. Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate Federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 10. Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other Federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (2) any employee of FRTIB in his or her official capacity, or (3) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (4) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 11. Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 12. NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other Federal Government agencies pursuant to the Federal Records Act. 13. Security Threat: A record from this system of records may be disclosed to Federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS**: Records are maintained in paper and electronic form, including on computer databases and cloud-based services, all of which are securely stored. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS**: Records are retrieved by employee/contractor name or user ID. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS**: These records are maintained in accordance with General Records Schedule 3.2 (Information Systems Security Records), Items 030 and 031, issued by the National Archives and Records Administration (NARA). **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS**: FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB’s security program to protect the security, confidentiality, availability, and integrity of the information and to ensure that records are not disclosed to or accessed by unauthorized individuals. **RECORD ACCESS PROCEDURES:** Individuals seeking to access records within this system must submit a request pursuant to [5 CFR part 1630]({{ site.baseurl }}/exit/?idx=158). Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **HISTORY:** None. </div> </li> <!-- FRTIB-22 --> <li id="frtib-22"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a22"> FRTIB-22 | Cybersecurity Investigation Records </button> <div id="a22" class="usa-accordion-content" markdown="1"> **Federal Register** [85 FR 52132]({{ site.baseurl }}/exit/?idx=75) **SYSTEM NAME AND NUMBER:** FRTIB-22, Cybersecurity Investigation Records. **SECURITY CLASSIFICATION:** Unclassified. **SYSTEM LOCATION:** Records are located at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be kept at an additional location for Business Continuity purposes. **SYSTEM MANAGER:** Chief Technology Officer, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002, (202) 942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM:** 5 U.S.C. 8474; and 44 U.S.C. 3101. **PURPOSES OF THE SYSTEM:** The records in this system of records are used to investigate and prevent potential intrusions into FRTIB network boundaries, to investigate and prevent misuse of information within FRTIB’s network boundaries, and to investigate and prevent the compromise or misuse of FRTIB information. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:** This system of records contains information on Thrift Savings Plan (TSP) participants and beneficiaries, FRTIB employees, FRTIB contractors, and any third party individuals with access to FRTIB systems, networks, computers, or data, or those have been alleged to have accessed or attempted to access FRTIB systems, networks, computers, or data without authorization. **CATEGORIES OF RECORDS IN THE SYSTEM:** Records in this system include: first and last name, telephone number, username, e-mail address, media access control (MAC) address, internet protocol (IP) address, and network traffic data, and logs. Because network monitoring tools and security tools are used to analyze email and network traffic and to monitor user activity on FRTIB’s network, these tools can capture a variety of data types including but not limited to: name; social security number; TSP account number; date of birth; address; email address; and financial information. **RECORD SOURCE CATEGORIES:** Records are provided by the Agency’s network monitoring tools and the Agency’s security tools. The network monitoring tools inspect incoming and outgoing network traffic and include the Agency’s data loss prevention (DLP) capabilities. The security tools analyze user activity within the FRTIB network and include the Agency’s security information and event management tool. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND THE PURPOSES OF SUCH USES:** Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, as amended, 5 U.S.C. § 552a(b); and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Breach Mitigation and Notification: Response to Breach of FRTIB Records: A record from this system of records may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records; (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB’s efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 3. Routine Use&#8212;Response to Breach of Other Records: A record from this system of records may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. 4. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 5. Routine Use&#8212;Contractors, et al.: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 6. Routine Use&#8212;Investigations, Third Parties: A record from this system of records may be disclosed to third parties during the course of a law enforcement investigation to the extent necessary to obtain information pertinent to the investigation, provided disclosure is appropriate to the proper performance of the official duties of the third party officer making the disclosure. 7. Routine Use&#8212;Investigations, Other Agencies: A record from this system of records may be disclosed to appropriate Federal, state, local, tribal, or foreign government agencies or multilateral governmental organizations for the purpose of investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, license, or treaty where FRTIB determines that the information would assist in the enforcement of civil or criminal laws. 8. Routine Use&#8212;Law Enforcement Intelligence: A record from this system of records may be disclosed to a Federal, state, tribal, local, or foreign government agency or organization, or international organization, lawfully engaged in collecting law enforcement intelligence information, whether civil or criminal, or charged with investigating, prosecuting, enforcing or implementing civil or criminal laws, related rules, regulations or orders, to enable these entities to carry out their law enforcement responsibilities, including the collection of law enforcement intelligence. 9. Routine Use&#8212;Law Enforcement Referrals: A record from this system of records may be disclosed to an appropriate Federal, state, tribal, local, international, or foreign agency or other appropriate authority charged with investigating or prosecuting a violation or enforcing or implementing a law, rule, regulation, or order, where a record, either on its face or in conjunction with other information, indicates a violation or potential violation of law, which includes criminal, civil, or regulatory violations and such disclosure is proper and consistent with the official duties of the person making the disclosure. 10. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB’s outside counsel, other Federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (2) any employee of FRTIB in his or her official capacity, or (3) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (4) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 11. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 12. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other Federal Government agencies pursuant to the Federal Records Act. 13. Routine Use&#8212;Security Threat: A record from this system of records may be disclosed to Federal and foreign government intelligence or counterterrorism agencies when FRTIB reasonably believes there to be a threat or potential threat to national or international security for which the information may be useful in countering the threat or potential threat, when FRTIB reasonably believes such use is to assist in anti-terrorism efforts, and disclosure is appropriate to the proper performance of the official duties of the person making the disclosure. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS:** Records are maintained in electronic form, including on computer databases and cloud-based services, all of which are securely stored. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:** Records are retrieved by name, e-mail address, log identification number, internet protocol (IP) address, media access control (MAC) address, or FRTIB username. **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:** These records are maintained in accordance with General Records Schedule 3.1 (General Technology Management Records), items 11 or 20 or GRS 3.2 (Information System Security Records) item 10, 30, and 31 issued by the National Archives and Records Administration (NARA). **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:** FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB’s security program to protect the security, confidentiality, availability, and integrity of the information, and to ensure that records are not disclosed to or accessed by unauthorized individuals. Electronic records are stored on computer systems and protected by role-based access to users with passwords set by authorized users that must be changed periodically. **RECORD ACCESS PROCEDURES:** Individuals seeking to access records within this system must submit a request pursuant to 5 CFR Part 1630. Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as Power of Attorney, in order for the representative to act on their behalf. **CONTESTING RECORDS PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** None. **HISTORY:** None. </div> </li> <!-- FRTIB-23 --> <li id="frtib-23"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="a23"> FRTIB-23 | Insider Threat Program Records </button> <div id="a23" class="usa-accordion-content" markdown="1"> **Federal Register** [84 FR 40564]({{ site.baseurl }}/exit/?idx=74). **SYSTEM NAME AND NUMBER**: FRTIB-23, Insider Threat Program Records. **SECURITY CLASSIFICATION**: Unclassified. **SYSTEM LOCATION**: Records are located at the Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002. Records may also be maintained at the business offices of third-party service providers. Records may also be maintained at additional locations for Business Continuity purposes. **SYSTEM MANAGER**: Insider Threat Program Manager, Federal Retirement Thrift Investment Board, 77 K Street NE, Suite 1000, Washington, DC 20002, (202) 942-1600. **AUTHORITY FOR MAINTENANCE OF THE SYSTEM**: [5 U.S.C. 8474]({{ site.baseurl }}/exit/?idx=157); 44 U.S.C. Chapter 35; [44 U.S.C. 3101]({{ site.baseurl }}/exit/?idx=73). **PURPOSE(S) OF THE SYSTEM**: FRTIB's Insider Threat Program is being implemented to prevent, detect, and mitigate the effects of insider threats, defined as, “the potential for an individual who has or had authorized access to an organization's assets to use their access, either maliciously or unintentionally, to act in a way that could negatively affect the organization.” The Insider Threat Program system of records is being established to manage insider threat matters; facilitate insider threat activities, inquiries, and investigations; identify insider threats to FRTIB facilities, information, and information systems; track referrals of potential insider threats from FRTIB's hotline; and to track referrals of potential insider threats to internal and external partners. **CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM**: This system collects information on current or former FRTIB employees, contractors, subcontractors, or any other individuals who have or have previously had authorized access to FRTIB facilities, information, or information systems. **CATEGORIES OF RECORDS IN THE SYSTEM**: The categories of records compiled for each insider threat report, inquiry, or investigation may vary significantly based on the nature of each actual or potential insider threat incident. Categories of records in the Insider Threat Program system of records may include name; social security number; date of birth; place of birth; personal and business email address; personal and business phone number; work history; background investigation information (including any information derived from SF-85, SF-85P, and SF-86 forms and background investigation processes); user ID; user activity performed on FRTIB devices; correspondence sent or received on an FRTIB device or network; personnel records (including disciplinary records and performance records); records of access to FRTIB facilities; records of security violations; reports from FRTIB's hotline for fraud, waste, abuse, and other misconduct; and law enforcement referrals. **RECORD SOURCE CATEGORIES**: To monitor, identify, and respond to potential insider threats, information in the system will be received on an as-needed basis depending on the nature of the inquiry or investigation from: FRTIB employees, contractors, vendors, or other individuals with access to FRTIB facilities, information, or information systems; FRTIB's hotline for reporting fraud, waste, abuse, and other misconduct; information collected through user activity monitoring; officials from other foreign, federal, tribal, state, and local government agencies and organizations; non-government, commercial, public, and private agencies and organizations; and from relevant records, including information security databases and files; personnel security databases and files; FRTIB human resources databases and files; access records for FRTIB facilities; FRTIB contractor files; FRTIB's Office of Technology Services; FRTIB telephone usage records; federal, state, tribal, territorial, and local law enforcement and investigatory records; other Federal agencies; and publicly available information. **ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES**: Information about covered individuals may be disclosed without consent as permitted by the Privacy Act of 1974, as amended, [5 U.S.C. 552a]({{ site.baseurl }}/exit/?idx=156)(b); and: 1. Routine Use&#8212;Audit: A record from this system of records may be disclosed to an agency, organization, or individual for the purpose of performing an audit or oversight operations as authorized by law, but only such information as is necessary and relevant to such audit or oversight function when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 2. Routine Use&#8212;Breach Mitigation and Notification: Response to Breach of FRTIB Records: A record from this system of records may be disclosed to appropriate agencies, entities, and persons when (1) FRTIB suspects or has confirmed that there has been a breach of the system of records; (2) FRTIB has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, FRTIB (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with FRTIB's efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm. 3. Routine Use&#8212;Response to Breach of Other Records: A record from this system of records may be disclosed to another Federal agency or Federal entity, when FRTIB determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach. 4. Routine Use&#8212;Congressional Inquiries: A record from this system of records may be disclosed to a Congressional office from the record of an individual in response to an inquiry from that Congressional office made at the request of the individual to whom the record pertains. 5. Routine Use&#8212;Contractors, et al.: A record from this system of records may be disclosed to contractors, grantees, experts, consultants, the agents thereof, and others performing or working on a contract, service, grant, cooperative agreement, interagency agreement, or other assignment for FRTIB, when necessary to accomplish an agency function related to this system of records. Individuals provided information under this routine use are subject to the same Privacy Act requirements and limitations on disclosure as are applicable to FRTIB officers and employees. 6. Routine Use&#8212;Third-Party Service Providers: A record from this system of records may be disclosed to third-party service providers, including other government agencies, such as the Department of Justice, that provide support for FRTIB's Insider Threat Program under a contract or interagency agreement. 7. Routine Use&#8212;Disclosure to Law Enforcement: Where a record, either alone or in conjunction with other information, indicates a violation or potential violation of law—criminal, civil, or regulatory in nature—the relevant records may be referred to the appropriate federal, state, local, territorial, tribal, or foreign law enforcement authority or other appropriate entity charged with the responsibility for investigating or prosecuting such violation or charged with enforcing or implementing such law. 8. Routine Use&#8212;Litigation, DOJ or Outside Counsel: A record from this system of records may be disclosed to the Department of Justice, FRTIB's outside counsel, other Federal agency conducting litigation or in proceedings before any court, adjudicative or administrative body, when: (1) FRTIB, or (2) any employee of FRTIB in his or her official capacity, or (3) any employee of FRTIB in his or her individual capacity where DOJ or FRTIB has agreed to represent the employee, or (4) the United States or any agency thereof, is a party to the litigation or has an interest in such litigation, and FRTIB determines that the records are both relevant and necessary to the litigation and the use of such records is compatible with the purpose for which FRTIB collected the records. 9. Routine Use&#8212;Litigation, Opposing Counsel: A record from this system of records may be disclosed to a court, magistrate, or administrative tribunal in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, or settlement negotiations or in connection with criminal law proceedings or in response to a subpoena. 10. Routine Use&#8212;NARA/Records Management: A record from this system of records may be disclosed to the National Archives and Records Administration (NARA) or other Federal Government agencies pursuant to the Federal Records Act. 11. Routine Use&#8212;Insider Threat Community of Practice: A record from this system of records may be disclosed to any Federal agency or group of agencies with responsibilities for activities related to counterintelligence or the detection of insider threats. **POLICIES AND PRACTICES FOR STORAGE OF RECORDS**: Records are maintained in paper and electronic form, including on computer databases and cloud-based services, all of which are securely stored. **POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS**: Records are retrieved by name, phone number, case number, or internal FRTIB identification (including FRTIB email, username, etc.). **POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS**: These records are maintained in accordance with General Records Schedule 5.6 (Security Records), Items 210 through 240, issued by the National Archives and Records Administration (NARA). **ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS**: FRTIB has adopted appropriate administrative, technical, and physical controls in accordance with FRTIB's security program to protect the security, confidentiality, availability, and integrity of the information and to ensure that records are not disclosed to or accessed by unauthorized individuals. Access to the records in this system is limited to individuals who have the appropriate permissions and who have a need to know the information in order to perform their official duties. **RECORD ACCESS PROCEDURES:** Individuals seeking to access records within this system must submit a request pursuant to [5 CFR part 1630]({{ site.baseurl }}/exit/?idx=158). Attorneys or other persons acting on behalf of an individual must provide written authorization from that individual, such as a Power of Attorney, in order for the representative to act on their behalf. **CONTESTING RECORD PROCEDURES:** See Record Access Procedures above. **NOTIFICATION PROCEDURES:** See Record Access Procedures above. **EXEMPTIONS PROMULGATED FOR THE SYSTEM:** Records in this system will be exempt, based on [5 U.S.C. 552a]({{ site.baseurl }}/exit/?idx=156)(k)(2), from the requirements in subsections (c)(3), (d)(1)-(4), (e)(1), (e)(4)(G)-(I), and (f) of the Privacy Act. The Agency has promulgated regulations implementing the Privacy Act at [5 CFR 1630.15]({{ site.baseurl }}/exit/?idx=76) that establish this exemption. **HISTORY:** None. </div> </li> </ul> ## The Agency also uses the following government-wide SORNs: <ul class="usa-accordion"> <!-- EEOC/GOVT-1 --> <li id="frtib-eeoc-govt-1"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="b1"> EEOC/GOVT-1 | Equal Employment Opportunity (EEO) in the Federal Government Complaint and Appeal Records </button> <div id="b1" class="usa-accordion-content" markdown="1"> **Summary of Purpose** Counsel, investigate, and adjudicate complaints of employment discrimination brought by applicants and current and former federal employees against federal employers **Federal Register** [81 Fed. Reg. 81116, 81135 (Nov. 17, 2016)]({{ site.baseurl }}/exit/?idx=56) (replaced FRTIB-3) </div> </li> <!-- OPM/GOVT-1 --> <li id="frtib-opm-govt-1"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="b2"> OPM/GOVT-1 | General Personnel Records </button> <div id="b2" class="usa-accordion-content" markdown="1"> **Summary of Purpose** Give legal force and effect to personnel transactions and establishment employee rights and benefits under pertinent laws and regulations governing Federal employment **Federal Register** [77 Fed. Reg. 73694 (Dec. 11, 2012)]({{ site.baseurl }}/exit/?idx=57) [76 Fed. Reg. 32997 (June 7, 2011)]({{ site.baseurl }}/exit/?idx=58) [71 Fed. Reg. 35341 (June 19, 2006)]({{ site.baseurl }}/exit/?idx=59) [65 Fed. Reg. 24731 (April 27, 2000)]({{ site.baseurl }}/exit/?idx=60) [61 Fed. Reg. 36919 (July 15, 1996)]({{ site.baseurl }}/exit/?idx=61) (replaced FRTIB-4) </div> </li> <!-- OPM/GOVT-2--> <li id="frtib-opm-govt-2-"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="b3"> OPM/GOVT-2 | Employee Performance File System Records </button> <div id="b3" class="usa-accordion-content" markdown="1"> **Summary of Purpose** Ensure that all appropriate records on an employee’s performance are retained and available (1) To agency officials having a need for the information; (2) to employees; (3) to support actions based on the records; (4) for use by the OPM in connection with its personnel management evaluation role in the executive branch; and (5) to identify individuals for personnel research **Federal Register** [71 Fed. Reg. 35341 (June 19, 2006)]({{ site.baseurl }}/exit/?idx=59) [65 Fed. Reg. 24731 (April 27, 2000)]({{ site.baseurl }}/exit/?idx=60) [61 Fed. Reg. 36919 (July 15, 1996)]({{ site.baseurl }}/exit/?idx=61) (replaced FRTIB-4) </div> </li> <!-- OPM/GOVT-3 --> <li id="frtib-opm-govt-3"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="b4"> OPM/GOVT-3 | Records of Adverse Actions, Performance Based Reduction in Grade and Removal Actions, and Termination of Probationers </button> <div id="b4" class="usa-accordion-content" markdown="1"> **Summary of Purpose** Records resulting from the proposal, processing, and documentation of actions taken either by the OPM or by agencies against employees **Federal Register** [71 Fed. Reg. 35341 (June 19, 2006)]({{ site.baseurl }}/exit/?idx=59) [65 Fed. Reg. 24731 (April 27, 2000)]({{ site.baseurl }}/exit/?idx=60) [61 Fed. Reg. 36919 (July 15, 1996)]({{ site.baseurl }}/exit/?idx=61) (replaced FRTIB-4) </div> </li> <!-- OGE/GOVT-1 --> <li id="frtib-oge-govt-1"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="b5"> OGE/GOVT-1 | Executive Branch Personnel Public Financial Disclosure Reports and Other Name-Retrieved Ethics Program Records </button> <div id="b5" class="usa-accordion-content" markdown="1"> **Summary of Purpose** Maintained in accordance with the requirements of the Ethics in Government Act of 1978 and the Ethics Reform Act of 1989, as amended, and Executive Order 12674 as modified, and OGE and agency regulations thereunder **Federal Register** [78 Fed. Reg. 73863 (Dec. 9, 2013)]({{ site.baseurl }}/exit/?idx=62) [76 Fed. Reg. 24489 (May 2, 2011)]({{ site.baseurl }}/exit/?idx=63), as modified at [77 Fed. Reg. 45353 (July 31, 2012)](h{{ site.baseurl }}/exit/?idx=64) [68 Fed. Reg. 3098 (Jan. 22, 2003)]({{ site.baseurl }}/exit/?idx=65), as corrected at [68 Fed. Reg. 24744 (May 8, 2003)]({{ site.baseurl }}/exit/?idx=66) (replaced FRTIB-8, FRTIB-11) </div> </li> <!-- OGE/GOVT-2 --> <li id="frtib-oge-govt-2"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="b6"> OGE/GOVT-2 | Executive Branch Confidential Financial Disclosure Reports </button> <div id="b6" class="usa-accordion-content" markdown="1"> **Summary of Purpose** Maintained to meet the requirements of Executive Order 12674 as modified, 5 CFR part 2634, agency regulations thereunder, as well as section 107 of the Ethics in Government Act of 1978, as amended, concerning the filing of confidential financial disclosure reports **Federal Register** [68 Fed. Reg. 3098 (Jan. 22, 2003)]({{ site.baseurl }}/exit/?idx=65), as corrected at [68 Fed. Reg. 24744 (May 8, 2003)]({{ site.baseurl }}/exit/?idx=66) (replaced FRTIB-11) </div> </li> <!-- GSA/GOVT-7 --> <li id="frtib-gsa-govt-7"> <button class="usa-accordion-button" aria-expanded="false" aria-controls="b7"> GSA/GOVT-7 | Federal Personal Identity Verification Identity Management System (PIV IDMS) </button> <div id="b7" class="usa-accordion-content" markdown="1"> **Summary of Purpose** Ensure the safety and security of Federal facilities, systems, or information, and of facility occupants and users; to provide for interoperability and trust in allowing physical access to individuals entering Federal facilities; and to allow logical access to federal information systems, networks, and resources on a government-wide basis **Federal Register** [80 Fed. Reg. 64416 (Oct. 23, 2015)]({{ site.baseurl }}/exit/?idx=67) (replaced FRTIB-10) </div> </li> </ul> <!-- CONTENT END -->

eng_Latn

f7a337d60b7a9ca7502f3a247aff5dfbc0df1a1f

md

Markdown

reference/docs-conceptual/getting-started/cookbooks/Working-with-Objects.md

omiossec/powerShell-Docs.fr-fr

15fe0e69e5884e79b07f90e590c3cd80781ed43b

reference/docs-conceptual/getting-started/cookbooks/Working-with-Objects.md

omiossec/powerShell-Docs.fr-fr

15fe0e69e5884e79b07f90e590c3cd80781ed43b

reference/docs-conceptual/getting-started/cookbooks/Working-with-Objects.md

omiossec/powerShell-Docs.fr-fr

15fe0e69e5884e79b07f90e590c3cd80781ed43b

--- ms.date: 06/05/2017 keywords: powershell,applet de commande title: Utilisation d’objets ms.assetid: 7ecc94a4-015c-4459-ae58-85289ea09030 ms.openlocfilehash: 5d86e1658286055f8a7dc57d488a6adcef577a10 ms.sourcegitcommit: cf195b090b3223fa4917206dfec7f0b603873cdf ms.translationtype: HT ms.contentlocale: fr-FR ms.lasthandoff: 04/09/2018 ms.locfileid: "30949653" --- # <a name="working-with-objects"></a>Utilisation d’objets Nous avons expliqué comment Windows PowerShell utilise des objets pour échanger des données entre applets de commande, et présenté quelques manières d’afficher des informations détaillées sur les objets à l’aide d’applets de commande Get-Member et Format pour consulter des propriétés particulières d’objets. La puissance des objets est qu’ils donnent accès à un grand nombre de données complexes et déjà corrélées. Quelques techniques simples permettent de manipuler davantage des objets pour faire plus de travail. Ce chapitre examine certains des types spécifiques d’objets et les méthodes permettant de les manipuler.

fra_Latn

f7a51e754ad0d6e8fc7f5ffd3ec32e464567255c

md

Markdown

src/pages/content/party-hunter.md

featureseditor/main-website

55a89e87e47fa84bccfcf09d5093f0d0d6ca5cff

src/pages/content/party-hunter.md

featureseditor/main-website

55a89e87e47fa84bccfcf09d5093f0d0d6ca5cff

2019-09-15T15:14:15.000Z

2020-09-13T19:00:07.000Z

src/pages/content/party-hunter.md

featureseditor/main-website

55a89e87e47fa84bccfcf09d5093f0d0d6ca5cff

2019-09-22T23:56:12.000Z

2020-07-26T19:26:17.000Z

--- title: "Party Hunter" slug: "party-hunter" issue: "Spring" issue_full_name: "Spring 2016" year: "2016" date: "2016-03-01" authors: ['Alistair Debling'] section: "art" audio: [] main_image: "" banner_image: "" images: ['debling.png'] videos: [] --- Single-channel video     04:28 minutes looped

eng_Latn

f7a5c5c21527222ddb5061086bdc02bd5fe122a8

md

Markdown

README.md

jeannzk021/Be-The-Hero-

4c87f8187b754b1aace887e55a4e401561ed043b

README.md

jeannzk021/Be-The-Hero-

4c87f8187b754b1aace887e55a4e401561ed043b

2021-05-11T08:31:16.000Z

2021-09-02T08:51:56.000Z

README.md

jeannzk021/Be-The-Hero-

4c87f8187b754b1aace887e55a4e401561ed043b

<h1 align="center"> 💻 Be The Hero - WEB 💻 <h5> Clique nas imagens 😎 <h5> - 🚀 <a href="https://github.com/jeannzk021/Be-The-Hero-#technologies">Technologies</a> - 🏠 <a href="https://github.com/jeannzk021/Be-The-Hero-#project">Project</a> - 🚩 <a href="https://github.com/jeannzk021/Be-The-Hero-#how-to-contribute">How to contribute</a> - 💻 <a href="https://github.com/jeannzk021/Be-The-Hero-#license">License</a>    ## Technologies This project was developed with the following technologies: - [Node.js](https://nodejs.org/en/) - [React](https://reactjs.org) - [React Native](https://facebook.github.io/react-native/) ## Project The project is intended for people who want to help cases registered with ONGs. ## How to contribute - Make a fork; - Create a branck with your feature: `git checkout -b my-feature`; - Commit changes: `git commit -m 'feat: My new feature'`; - Make a push to your branch: `git push origin my-feature`. After merging your receipt request to done, you can delete a branch from yours. ## License This project is under the MIT license. See the [LICENSE](https://github.com/jeannzk021/Be-The-Hero-) for details. --- by Jean Machado :wave: [Get in touch!](https://www.linkedin.com/in/jeanmachado021)

eng_Latn

f7a5df7073e5a99651783f617bb43eaae537f767

md

Markdown

builds/471.md

Sparrow-lang/perf-monitoring

dbac75a1910fe6c13f1c54ccd31c23a8b8e25b35

builds/471.md

Sparrow-lang/perf-monitoring

dbac75a1910fe6c13f1c54ccd31c23a8b8e25b35

builds/471.md

Sparrow-lang/perf-monitoring

dbac75a1910fe6c13f1c54ccd31c23a8b8e25b35

--- layout: build build-id: "471" title: "Build #471" date: Sun, 05 May 2019 18:02:54 +0000 ---

eng_Latn

f7a5f6e1c485823e3bdfa2e10b9ef46ce863c67f

md

Markdown

CONTRIBUTING.md

tksventures/reli-proxy

b1caa5f0d8b974e1d28503b742926f41eaf57ff3

2019-01-28T12:54:03.000Z

2019-02-11T13:56:17.000Z

CONTRIBUTING.md

iamonuwa/reli-proxy

d9c3c4c6bcefb156202a03bc09ad86b2d6b53964

2019-01-07T10:35:24.000Z

2020-01-13T21:33:06.000Z

CONTRIBUTING.md

iamonuwa/reli-proxy

d9c3c4c6bcefb156202a03bc09ad86b2d6b53964

2019-01-31T00:05:24.000Z

2019-02-08T13:06:41.000Z

# Welcome! Hi and welcome to the Community! ## Workflow The work on this project, starts with an Issue, and follows [Github Flow](https://guides.github.com/introduction/flow/) ## Developer's Certificate of Origin 1.1 [source](https://developercertificate.org/) By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. ## Contact If case of questions, reach out to as at support@tokesplatform.org

eng_Latn

f7a64f5c7a06e990642f497566a8dd661a7a8f79

md

Markdown

_definitions/bld-trinity-house.md

digitallawyer/openlegaldictionary

a318d6c73c3d8e33756d947add397dac7f25cca2

2018-08-07T21:57:01.000Z

2022-02-26T13:29:20.000Z

_definitions/bld-trinity-house.md

digitallawyer/openlegaldictionary

a318d6c73c3d8e33756d947add397dac7f25cca2

2018-08-07T22:29:07.000Z

2018-08-07T22:45:46.000Z

_definitions/bld-trinity-house.md

digitallawyer/openlegaldictionary

a318d6c73c3d8e33756d947add397dac7f25cca2

2020-12-26T17:22:04.000Z

2021-02-12T21:35:50.000Z

--- title: Trinity House letter: T permalink: "/definitions/bld-trinity-house.html" body: In English law. A society ait Deptford Strond, incorporated by Hen. VIII. in 1515, for the promotion of commerce and navigation by licensing and regulating pilots, and ordering and erecting beacons, light-houses, buoys, etc. wharton published_at: '2018-07-07' source: Black's Law Dictionary 2nd Ed (1910) layout: post ---

eng_Latn

f7a751d738066b1b76900f04bc7c3e09090e866e

md

Markdown

History.md

storify/logule

809626d30424dc52323f21820b806748a250cc48

2016-05-12T18:23:31.000Z

2016-05-12T18:23:31.000Z

History.md

storify/logule

809626d30424dc52323f21820b806748a250cc48

History.md

storify/logule

809626d30424dc52323f21820b806748a250cc48

0.6.1 / 2012-02-25 ================== * 0.4 support removed was not strictly metioned in 0.6 pre launch but it does affect it, so minor version increase * Slight zalgo style tweak * Bump dependencies' versions 0.6.0 / 2012-02-25 ================== * Redesign pass around interface to be simpler for people who do not want to use DI all the time: * Global log levels via environment variables - see readme * .line() gets the line number from new Error()'s 1st stack frame directly rather than by parsing * .lock() instance method removed - prefer evars for proper filtering rather than encouraging avoiding the tree * removed makeMiddleware instance method and put it in the example folder instead * node 0.4 support is removed 0.5.6 / 2012-01-12 ================== * New instance method .allow() does the opposite of suppress. This ensures the more sensible behaviour of ressurection allowed across subs, rather than forcing modules below to use instances not part of the chain. 0.5.5 / 2011-12-14 ================== * Slight tweak to verifier (could not handle null elements before this version) 0.5.4 / 2011-12-13 ================== * CoffeeScript removed entirely - JSHint is better for safe JS (found a couple of implicit returns errors with CS that are now fixed) * Paths should work on windows (used unix slashes for version) 0.5.3 / 2011-12-06 ================== * Explicit coffee-script dependency removed - now each new version is recompiiled before release 0.5.2 / 2011-12-01 ================== * logger.data exposes a frozen object with the current namespaces and logule version * logule.verify(inst) will verify that another logule instance is compatible with this (using exposed data.version on prototype) 0.5.1 / 2011-11-27 ================== * logule.get('line') does not chain, like the other get() functions 0.5.0 / 2011-11-27 ================== * logule.line() for those cases where you quickly want to find what went wrong 0.4.1 / 2011-11-27 ================== * logule is fully testable 0.4.0 / 2011-11-26 ================== * require output is a new instance that can be used directly -> no `new` operator required - use `sub` liberally * experimental middleware generator included 0.3.0 / 2011-11-25 ================== * The `remove` method is now known as `suppress` * The `get` method result no longer allows chaining into different log methods (bug) * Bad fns requested to `suppress` and `get` will result in an internal log in such a way that you can determine quickly what you did wrong * Everything is properly encapsulated so that you can not break out of `suppress` and `get`calls 0.2.0 / 2011-11-24 ================== * Multiple namespaces can be passed to constructor * Padding option now set via the `pad` method * Return a sanitized copy of the current Logger's specified method with the `get` method * Return a sanitized copy of the current Logger instance with the `remove` method * Return a copy of the current Logger instance but with extra namespace(s) appended with the `sub` method 0.1.1 / 2011-11-24 ================== * First working version

eng_Latn

f7a7f8bd2f8b179507f35aa29aa192e221bdf032

md

Markdown

README.md

echoprotocol/echojs-ping

5885a2aea3c100f467c613061a3861b9f8f06285

README.md

echoprotocol/echojs-ping

5885a2aea3c100f467c613061a3861b9f8f06285

README.md

echoprotocol/echojs-ping

5885a2aea3c100f467c613061a3861b9f8f06285

# Ping [](https://travis-ci.com/echoprotocol/echojs-ping) [](https://github.com/echoprotocol/echojs-ping) [](https://www.npmjs.com/package/echojs-ping) [](https://www.npmjs.com/package/echojs-ping) Ping is the avatar generator for Echo Blockchain accounts by him username. Each Echo Blockchain account has its own unique avatar. Ping will help you get it. ## Install Ping ```bash npm i echojs-ping ``` ## Use Ping in your code ```javascript const { svgAvatar } = require('echojs-ping'); const accountSvg = svgAvatar('pixelplex', 100); ``` where `pixelplex` - an Echo account name, and `100` - an avatar size. And as result, you will receive the source of SVG. As example:  ### Use on server side The SVG rendering requires DOM. If you want to use this library on the server, you should use the [svgdom](https://www.npmjs.com/package/svgdom) library ```javascript const window = require('svgdom'); const { svgAvatar } = require('echojs-ping'); const accountSvg = svgAvatar('pixelplex', 100, window); ``` ## License The MIT License (MIT) Copyright (c) 2019 Echo Technological Solutions LLC Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

eng_Latn

f7a870d086f9c1c74a0475aef55de5f63e756b2a

markdown

Markdown

_posts/2017-09-04-relaxing.markdown

elken/humanity

00f1f633cf36002c956965de4c211b55fd2744b8

_posts/2017-09-04-relaxing.markdown

elken/humanity

00f1f633cf36002c956965de4c211b55fd2744b8

_posts/2017-09-04-relaxing.markdown

elken/humanity

00f1f633cf36002c956965de4c211b55fd2744b8

--- title: Relaxing date: 2017-09-04 15:45:00 Z --- We are starting a new chill out Wednesday from 1400-1700. Music, films, art and games etc. All welcome. See you there! xx 

eng_Latn

f7a8d01b04bdcc0906511763fe5e100a4e63f42b

md

Markdown

README.md

RickChen13/MonitorWebSocketServer

dff264c4de835883ba89244e3d0e91e47a817312

README.md

RickChen13/MonitorWebSocketServer

dff264c4de835883ba89244e3d0e91e47a817312

README.md

RickChen13/MonitorWebSocketServer

dff264c4de835883ba89244e3d0e91e47a817312

# 系统监控使用WebSocket推送 > 目前已经实现功能 > > * cpu使用率、温度、功率监控 > * gpu使用率监控 > * 内存使用率监控 > * 磁盘占用情况监控 ## 使用方式 下载[最新编译文件](https://github.com/RickChen13/MonitorWebSocketServer/releases/latest)并解压。双击`start.cmd`文件即可启动，查看数据请参考连接示例 ## 连接示例 ### js连接示例 随便打开一个浏览器然后按下`F12`，并将以下代码粘贴进控制台后按下回车即可看到数据 ~~~javascript let ws = new WebSocket("ws://127.0.0.1:9901/GetMonitro"); ws.onopen = () => { console.log("is opend~"); }; ws.onmessage = (ev) => { let msg = ev.data; let wsData; try { wsData = JSON.parse(msg); } catch (error) { console.error(error); return; } console.log(wsData); }; ws.onclose = () => { console.log("is colsed~"); }; ws.onerror = (ev) => { console.log(ev); }; ~~~

yue_Hant

f7a94fdda0e6330974d771759bad4db84c1a59ed

md

Markdown

Lab8/README.md

adaneshp/Cloud-Native-Application-Architecture

6f2c00cea99677a7ed165bca9b9d2fd7e965e307

Lab8/README.md

adaneshp/Cloud-Native-Application-Architecture

6f2c00cea99677a7ed165bca9b9d2fd7e965e307

Lab8/README.md

adaneshp/Cloud-Native-Application-Architecture

6f2c00cea99677a7ed165bca9b9d2fd7e965e307

# Lab 8 : MongoDB - This code was developed in March, 2022. MongoDB is among the most popular of the NoSQL document stores for Cloud Native applications. ## Installation Now that you are familiar with Docker from Lab 7, we can run MongoDB in a Docker container, conveniently downloaded from DockerHub ``` sudo docker run -d -p 27017-27019:27017-27019 --name mongodb mongo:latest ``` Verify container is running ``` sudo docker container ls ``` ## MongoDB shell To access Mongo shell ``` sudo docker exec -it mongodb mongo ``` Let’s try out a few of the MongoDB CRUD operations (from https://docs.mongodb.com/manual/) MongoDB stores data records as documents (specifically BSON documents) which are gathered together in collections. BSON stands for Binary Javascript Object Notation. It is a binary-encoded serialization of JSON documents. A database stores one or more collections of documents. To select a database to use, in the mongo shell, issue the use db statement, as in the following example: ``` Note: > is the mongo shell prompt > use myDB ``` ## Create (Insert) db.collection.insertOne() inserts a single document into a collection. If the collection does not currently exist, insert operations will create the collection. ``` > db.inventory.insertOne( { item: "canvas", qty: 100, tags: ["cotton"], size: { h: 28, w: 35.5, uom: "cm" } } ) ``` Insert multiple documents ``` > db.inventory.insertMany([ { item: "journal", qty: 25, size: { h: 14, w: 21, uom: "cm" }, status: "A" }, { item: "notebook", qty: 50, size: { h: 8.5, w: 11, uom: "in" }, status: "A" }, { item: "paper", qty: 100, size: { h: 8.5, w: 11, uom: "in" }, status: "D" }, { item: "planner", qty: 75, size: { h: 22.85, w: 30, uom: "cm" }, status: "D" }, { item: "postcard", qty: 45, size: { h: 10, w: 15.25, uom: "cm" }, status: "A" } ]); ``` ## Query (Read) To select all documents in the collection, pass an empty document as the query filter parameter to the find method. The query filter parameter determines the select criteria: ``` > db.inventory.find( {} ) ``` Equality condition The following example selects from the inventory collection all documents where the status equals "D": ``` > db.inventory.find( { status: "D" } ) AND conditions > db.inventory.find( { status: "A", qty: { $lt: 30 } } ) OR conditions > db.inventory.find( { status: "A", $or: [ { qty: { $lt: 30 } }, { item: /^p/ } ] } ) ``` ## Update The following example uses the db.collection.updateOne() method on the inventory collection to update the first document where item equals "paper": ``` > db.inventory.updateOne( { item: "paper" }, { $set: { "size.uom": "cm", status: "P" }, $currentDate: { lastModified: true } } ) ``` uses the $set operator to update the value of the size.uom field to "cm" and the value of the status field to "P"; uses the $currentDate operator to update the value of the lastModified field to the current date. If lastModified field does not exist, $currentDate will create the field. The following example uses the db.collection.updateMany() method on the inventory collection to update all documents where qty is less than 50 ``` > db.inventory.updateMany( { "qty": { $lt: 50 } }, { $set: { "size.uom": "in", status: "P" }, $currentDate: { lastModified: true } } ) ``` uses the $set operator to update the value of the size.uom field to "in" and the value of the status field to "P"; uses the $currentDate operator to update the value of the lastModified field to the current date. If lastModified field does not exist, $currentDate will create the field The following example replaces the first document from the inventory collection where item: "paper": ``` > db.inventory.replaceOne( { item: "paper" }, { item: "paper", instock: [ { warehouse: "A", qty: 60 }, { warehouse: "B", qty: 40 } ] } ) ``` ## Delete The following example deletes the first document where status is "D" ``` > db.inventory.deleteOne( { status: "D" } ) ``` The following example removes all documents from the inventory collection where the status field equals "A": ``` > db.inventory.deleteMany({ status : "A" }) ``` The following example deletes all documents from the inventory collection: ``` > db.inventory.deleteMany({}) ``` ## Exit shell ``` > exit ``` ## Using MongoDB with Go MongoDB Go driver enables you to programmatically access MongoDB with Go code. Make a new lab8-mongodb directory. Install the MongoDB Go driver ``` go get go.mongodb.org/mongo-driver ``` Download the mongo.go code. Note how insertOne and findOne are done from the code. ``` $ go run mongo.go ``` If missing dependencies, go get the dependencies listed Note: Be sure to use docker container inspect <container name> to determine the mongodb container IP address. Update the go code with this IP address. This code is from the blog and github repo of Victor Tavares. See the repo for examples of other MongoDB operations A more complete description is available in the GoDocs including client side encryption https://pkg.go.dev/go.mongodb.org/mongo-driver/mongo Note: Many examples on the internet use the mgo library which is no longer maintained. Avoid these. Extra In Lab 7 we containerized the web server of Lab 4. The application used a map to simulate a database. Replace the map with MongoDB. That is, all data associated with the application will be stored in MongoDB. Feel free to change the type of data that you are storing (for example, blog posts instead of product information). Run MongoDB and the web server as two separate containers. Test your application using curl. Note: A typical three tier web application consists of a web server, an application server hosting business logic, and a database server.

eng_Latn

f7a97b4f9149f9adfb615c95aae66654478bc9fa

md

Markdown

RELEASE_CHECKLIST.md

hansihe/html5ever_elixir

832d9e785af813bf2216a35ee0d15a4d3e394ddc

2017-01-24T08:36:08.000Z

2019-10-10T01:15:13.000Z

RELEASE_CHECKLIST.md

hansihe/ex_html5ever

78574a42f5917e5f189ffd1eed21e0dd33d9b0e6

2017-02-03T07:51:34.000Z

2019-12-03T10:46:29.000Z

RELEASE_CHECKLIST.md

hansihe/ex_html5ever

78574a42f5917e5f189ffd1eed21e0dd33d9b0e6

2017-01-24T23:02:24.000Z

2019-10-18T13:20:16.000Z

# Release checklist In order to release a new version to Hex.pm we first need to: 1. write the changes in the `CHANGELOG.md` file 2. update the `README.md`, `CHANGELOG.md` and `mix.exs` with the new version 3. commit and create a tag for that version 4. push the changes to the repository with: `git push origin master --tags` 5. wait the CI to build all release files 6. run `mix rustler.download Html5ever.Native --all --print` 7. copy the output of the mix task and add to the release notes 8. run `mix hex.publish` and **make sure the checksum file is present** in the list of files to be published. It's important to ensure that we publish the checksum file with the package because otherwise the users won't be able to use the lib with precompiled files. They will need to always enforce compilation.

eng_Latn